linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kselftest@vger.kernel.org
Subject: [PATCH 2/6] selftests: powerpc/ptrace: Remove clean rule
Date: Tue, 23 Oct 2018 16:46:53 +1030	[thread overview]
Message-ID: <20181023061657.18007-3-joel@jms.id.au> (raw)
In-Reply-To: <20181023061657.18007-1-joel@jms.id.au>

When running 'make ptrace':

 make[1]: Entering directory 'tools/testing/selftests/powerpc/ptrace'
 Makefile:18: warning: overriding recipe for target 'clean'
 ../../lib.mk:137: warning: ignoring old recipe for target 'clean'

The rule is unnecessary as TEST_GEN_FILES are cleaned up by the rule in
lib.mk.

Signed-off-by: Joel Stanley <joel@jms.id.au>
---
 tools/testing/selftests/powerpc/ptrace/Makefile | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/tools/testing/selftests/powerpc/ptrace/Makefile b/tools/testing/selftests/powerpc/ptrace/Makefile
index e9a3850aae86..58de6d4a0cf4 100644
--- a/tools/testing/selftests/powerpc/ptrace/Makefile
+++ b/tools/testing/selftests/powerpc/ptrace/Makefile
@@ -13,6 +13,3 @@ ptrace-pkey core-pkey: child.h
 ptrace-pkey core-pkey: LDLIBS += -pthread
 
 $(TEST_GEN_PROGS): ../harness.c ../utils.c ../lib/reg.S ptrace.h
-
-clean:
-	rm -f $(TEST_GEN_PROGS) *.o
-- 
2.19.1


  parent reply	other threads:[~2018-10-23  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  6:16 [PATCH 0/6] selftests: powerpc build fixes Joel Stanley
2018-10-23  6:16 ` [PATCH 1/6] selftests: powerpc/ptrace: Make tests build Joel Stanley
2018-10-23  6:16 ` Joel Stanley [this message]
2018-10-23  6:16 ` [PATCH 3/6] selftests: powerpc/ptrace: Fix linking against pthread Joel Stanley
2018-10-23  6:16 ` [PATCH 4/6] selftests: powerpc/signal: Make tests build Joel Stanley
2018-10-23  6:16 ` [PATCH 5/6] selftests: powerpc/signal: Fix signal_tm CFLAGS Joel Stanley
2018-10-23  6:16 ` [PATCH 6/6] selftests: powerpc/pmu: Link ebb tests with -no-pie Joel Stanley

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=20181023061657.18007-3-joel@jms.id.au \
    --to=joel@jms.id.au \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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).