From: Michal Marek <mmarek@suse.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Russell King <linux@arm.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tony Luck <tony.luck@intel.com>,
Nathan Lynch <nathan_lynch@mentor.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] kbuild: drop FORCE from PHONY targets
Date: Tue, 15 Mar 2016 21:45:23 +0100 [thread overview]
Message-ID: <56E87463.9020300@suse.com> (raw)
In-Reply-To: <CALCETrVNMv5XwpXTJcevVLCfTSMbsqKsjzzukoGr7VAHuumFpg@mail.gmail.com>
Dne 15.3.2016 v 19:27 Andy Lutomirski napsal(a):
> Fair enough, although I'm curious why this happens. It might be worth
> changing the docs to say that .PHONY is *not* an substitute for FORCE
> in that context, then.
These two are unrelated, except that FORCE is redundant for a .PHONY
target. FORCE is our idiom to tell make to always remake the target and
let us handle the dependencies manually. Listing a target as .PHONY
tells make that the target will not produce a file of the same name
(typically, "all", "install", etc).
Michal
next prev parent reply other threads:[~2016-03-15 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 0:13 [PATCH] kbuild: drop FORCE from PHONY targets Masahiro Yamada
2016-03-14 0:39 ` Andy Lutomirski
2016-03-14 4:08 ` Masahiro Yamada
2016-03-14 4:28 ` Andy Lutomirski
2016-03-14 4:36 ` Masahiro Yamada
2016-03-14 4:44 ` Andy Lutomirski
2016-03-14 6:26 ` Masahiro Yamada
2016-03-15 18:27 ` Andy Lutomirski
2016-03-15 20:45 ` Michal Marek [this message]
2016-03-15 20:48 ` Andy Lutomirski
2016-03-17 3:52 ` Masahiro Yamada
2016-04-20 8:29 ` Michal Marek
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=56E87463.9020300@suse.com \
--to=mmarek@suse.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.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@arm.linux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=nathan_lynch@mentor.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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