From: David Laight <David.Laight@ACULAB.COM>
To: "'Michael Ellerman'" <mpe@ellerman.id.au>,
Shuah Khan <shuahkh@osg.samsung.com>,
"shuah@kernel.org" <shuah@kernel.org>,
"bamvor.zhangjian@linaro.org" <bamvor.zhangjian@linaro.org>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"paulus@samba.org" <paulus@samba.org>,
"dvhart@infradead.org" <dvhart@infradead.org>
Cc: "linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"dsafonov@virtuozzo.com" <dsafonov@virtuozzo.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"emilio.lopez@collabora.co.uk" <emilio.lopez@collabora.co.uk>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"luto@kernel.org" <luto@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"mingo@kernel.org" <mingo@kernel.org>
Subject: RE: [PATCH 8/8] selftests: x86: override clean in lib.mk to fix warnings
Date: Mon, 24 Apr 2017 15:57:34 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DCFFD9941@AcuExch.aculab.com> (raw)
In-Reply-To: <87o9vpyp6h.fsf@concordia.ellerman.id.au>
From: Linuxppc-dev Michael Ellerman
> Shuah Khan <shuahkh@osg.samsung.com> writes:
>
> > Add override for lib.mk clean to fix the following warnings from clean
> > target run.
> >
> > Makefile:44: warning: overriding recipe for target 'clean'
> > ../lib.mk:55: warning: ignoring old recipe for target 'clean'
> >
> > Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> > ---
> > tools/testing/selftests/x86/Makefile | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/x86/Makefile b/tools/testing/selftests/x86/Makefile
> > index 38e0a9c..4d27550 100644
> > --- a/tools/testing/selftests/x86/Makefile
> > +++ b/tools/testing/selftests/x86/Makefile
> > @@ -40,8 +40,9 @@ all_32: $(BINARIES_32)
> >
> > all_64: $(BINARIES_64)
> >
> > -clean:
> > +override define CLEAN
> > $(RM) $(BINARIES_32) $(BINARIES_64)
> > +endef
>
> Simpler as:
>
> EXTRA_CLEAN := $(BINARIES_32) $(BINARIES_64)
Actually for builds that insist on crapping all over the source tree I've used:
clean:
rm -rf `cat .cvsignore 2>/dev/null`
David
next prev parent reply other threads:[~2017-04-24 15:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 23:14 [PATCH 0/8] Fix clean target warnings Shuah Khan
2017-04-21 23:14 ` [PATCH 1/8] selftests: splice: fix clean target to not remove default_file_splice_read.sh Shuah Khan
2017-04-21 23:14 ` [PATCH 2/8] selftests: lib.mk: define CLEAN macro to allow Makefiles to override clean Shuah Khan
2017-04-22 5:38 ` Michael Ellerman
2017-04-25 13:36 ` Shuah Khan
2017-04-26 10:55 ` Michael Ellerman
2017-04-24 15:45 ` David Laight
2017-04-24 19:46 ` Shuah Khan
2017-04-21 23:14 ` [PATCH 3/8] selftests: futex: override clean in lib.mk to fix warnings Shuah Khan
2017-04-27 21:54 ` Darren Hart
2017-04-27 21:57 ` Shuah Khan
2017-04-21 23:14 ` [PATCH 4/8] selftests: gpio: " Shuah Khan
2017-04-22 5:40 ` Michael Ellerman
2017-04-25 15:02 ` Shuah Khan
2017-04-21 23:14 ` [PATCH 5/8] selftests: powerpc: " Shuah Khan
2017-04-21 23:14 ` [PATCH 6/8] selftests: splice: " Shuah Khan
2017-04-22 5:40 ` Michael Ellerman
2017-04-25 15:03 ` Shuah Khan
2017-04-21 23:14 ` [PATCH 7/8] selftests: sync: " Shuah Khan
2017-04-22 5:41 ` Michael Ellerman
2017-04-25 15:03 ` Shuah Khan
2017-04-21 23:14 ` [PATCH 8/8] selftests: x86: " Shuah Khan
2017-04-22 5:41 ` Michael Ellerman
2017-04-24 15:57 ` David Laight [this message]
2017-04-24 19:48 ` Shuah Khan
2017-04-25 15:03 ` Shuah Khan
2017-04-27 22:02 ` [PATCH 0/8] Fix clean target warnings Shuah Khan
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=063D6719AE5E284EB5DD2968C1650D6DCFFD9941@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=dave.hansen@linux.intel.com \
--cc=dsafonov@virtuozzo.com \
--cc=dvhart@infradead.org \
--cc=emilio.lopez@collabora.co.uk \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rkrcmar@redhat.com \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®