From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Tony Luck <tony.luck@intel.com>,
Russell King <linux@arm.linux.org.uk>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] kbuild: drop redundant "PHONY += FORCE"
Date: Mon, 25 Apr 2016 14:07:31 +0200 [thread overview]
Message-ID: <571E0883.5020904@suse.cz> (raw)
In-Reply-To: <CAK7LNATv51PRc9bGU7Q8_oTk9=C5ryfu7vMsKbG5drcgVbf1-Q@mail.gmail.com>
On 2016-04-20 10:56, Masahiro Yamada wrote:
> Hi Michal,
>
> 2016-04-20 17:47 GMT+09:00 Michal Marek <mmarek@suse.cz>:
>> On Fri, Apr 08, 2016 at 11:16:10AM +0900, Masahiro Yamada wrote:
>>> "PHONY += FORCE" is already cared by scripts/Makefile.build,
>>> which these files are included from.
>>
>> arch/ia64/Makefile is in fact included via the main Makefile. But this
>> one also has the PHONY += FORCE statement. Maybe we should initialize
>> PHONY with FORCE in Kbuild.include. Nevertheless, this patch is correct.
>>
>> Michal
>
> Ah, right.
>
> If it is not too late and you do not mind,
> could you rephrase the git-log?
Hi Masahiro,
I'd rather not rewrite the git log. It was just a minor nitpick and
there is not so much going on in arch/ia64 to cause confusion.
Michal
prev parent reply other threads:[~2016-04-25 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 2:16 [PATCH] kbuild: drop redundant "PHONY += FORCE" Masahiro Yamada
2016-04-20 8:47 ` Michal Marek
2016-04-20 8:56 ` Masahiro Yamada
2016-04-25 12:07 ` 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=571E0883.5020904@suse.cz \
--to=mmarek@suse.cz \
--cc=fenghua.yu@intel.com \
--cc=gxt@mprc.pku.edu.cn \
--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@arm.linux.org.uk \
--cc=tony.luck@intel.com \
--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