From: Wang Long <long.wanglong@huawei.com>
To: <shuahkh@osg.samsung.com>
Cc: <mpe@ellerman.id.au>, <mmarek@suse.com>,
<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<peifeiyue@huawei.com>
Subject: [PATCH v2] kselftest: add kselftest-clean rule
Date: Thu, 8 Oct 2015 02:41:18 +0000 [thread overview]
Message-ID: <1444272078-7087-1-git-send-email-long.wanglong@huawei.com> (raw)
In-Reply-To: <560E9242.9000402@osg.samsung.com>
We use
$make TARGETS="size timers" kselftest
to build and run selftests. but there is no rule
for us to clean the kselftest generated files.
This patch add the rules, for example:
$ make TARGETS="size timers" kselftest-clean
can clean all kselftest generated files.
Signed-off-by: Wang Long <long.wanglong@huawei.com>
---
Makefile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Makefile b/Makefile
index 1d341eb..3edd7b3 100644
--- a/Makefile
+++ b/Makefile
@@ -1075,6 +1075,9 @@ PHONY += kselftest
kselftest:
$(Q)$(MAKE) -C tools/testing/selftests run_tests
+kselftest-clean:
+ $(Q)$(MAKE) -C tools/testing/selftests clean
+
# ---------------------------------------------------------------------------
# Modules
@@ -1282,6 +1285,7 @@ help:
@echo ' kselftest - Build and run kernel selftest (run as root)'
@echo ' Build, install, and boot kernel before'
@echo ' running kselftest on it'
+ @echo ' kselftest-clean - Remove all generated kselftest files'
@echo ''
@echo 'Kernel packaging:'
@$(MAKE) $(build)=$(package-dir) help
--
1.8.3.4
next prev parent reply other threads:[~2015-10-08 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:33 [PATCH] kselftest: add cleankselftest rule Wang Long
2015-09-30 13:36 ` Shuah Khan
2015-10-01 1:17 ` Michael Ellerman
2015-10-02 14:18 ` Shuah Khan
2015-10-08 2:37 ` long.wanglong
2015-10-08 2:41 ` Wang Long [this message]
2015-10-08 3:52 ` [PATCH v2] kselftest: add kselftest-clean rule Michael Ellerman
2015-10-08 12:21 ` Michal Marek
2015-10-08 13:26 ` 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=1444272078-7087-1-git-send-email-long.wanglong@huawei.com \
--to=long.wanglong@huawei.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=mpe@ellerman.id.au \
--cc=peifeiyue@huawei.com \
--cc=shuahkh@osg.samsung.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
all inboxes | Powered by JetHome®