public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild@vger.kernel.org
Cc: Tony Luck <tony.luck@intel.com>,
	Nathan Lynch <nathan_lynch@mentor.com>,
	linux-ia64@vger.kernel.org, x86@kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	Andy Lutomirski <luto@amacapital.net>,
	Ingo Molnar <mingo@redhat.com>, Fenghua Yu <fenghua.yu@intel.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kbuild: drop FORCE from PHONY targets
Date: Wed, 20 Apr 2016 10:29:11 +0200	[thread overview]
Message-ID: <57173DD7.6020601@suse.com> (raw)
In-Reply-To: <1457828035-30584-1-git-send-email-yamada.masahiro@socionext.com>

Dne 13.3.2016 v 01:13 Masahiro Yamada napsal(a):
> These targets are marked as PHONY.  No need to add FORCE to their
> dependency.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
>  Makefile                     | 8 ++++----
>  arch/arm/vdso/Makefile       | 2 +-
>  arch/ia64/Makefile           | 4 ++--
>  arch/x86/entry/vdso/Makefile | 4 ++--
>  4 files changed, 9 insertions(+), 9 deletions(-)

Applied to kbuild.git#kbuild now, sorry for the delay.

Michal


      parent reply	other threads:[~2016-04-20  8:29 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
2016-03-15 20:48                 ` Andy Lutomirski
2016-03-17  3:52                   ` Masahiro Yamada
2016-04-20  8:29 ` 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=57173DD7.6020601@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