From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org
Cc: linux-mips@linux-mips.org, Tony Luck <tony.luck@intel.com>,
x86@kernel.org, linux-ia64@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Russell King <linux@arm.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
user-mode-linux-user@lists.sourceforge.net,
Ingo Molnar <mingo@redhat.com>, Fenghua Yu <fenghua.yu@intel.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] kbuild: refactor Makefile inclusion
Date: Thu, 02 Apr 2015 17:27:49 +0200 [thread overview]
Message-ID: <551D5FF5.7070503@suse.cz> (raw)
In-Reply-To: <1427456618-23830-1-git-send-email-yamada.masahiro@socionext.com>
On 2015-03-27 12:43, Masahiro Yamada wrote:
> Masahiro Yamada (4):
> kbuild: use relative path to include Makefile
> kbuild: use relative path more to include Makefile
> kbuild: include $(src)/Makefile rather than $(obj)/Makefile
> kbuild: ia64: use $(src)/Makefile.gate rather than particular path
Applied to kbuild.git#kbuild.
Michal
prev parent reply other threads:[~2015-04-02 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 11:43 [PATCH 0/4] kbuild: refactor Makefile inclusion Masahiro Yamada
2015-03-27 11:43 ` [PATCH 1/4] kbuild: use relative path to include Makefile Masahiro Yamada
2015-03-27 11:43 ` [PATCH 2/4] kbuild: use relative path more " Masahiro Yamada
2015-03-27 11:43 ` [PATCH 3/4] kbuild: include $(src)/Makefile rather than $(obj)/Makefile Masahiro Yamada
2015-03-27 11:43 ` [PATCH 4/4] kbuild: ia64: use $(src)/Makefile.gate rather than particular path Masahiro Yamada
2015-04-02 15:27 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551D5FF5.7070503@suse.cz \
--to=mmarek@suse.cz \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).