From: Rui Teng <rui.teng@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com,
Rui Teng <rui.teng@linux.vnet.ibm.com>
Subject: [PATCH] perf: Skip running the feature tests for 'make install-doc'
Date: Wed, 10 Aug 2016 16:49:08 +0800 [thread overview]
Message-ID: <1470818948-17784-1-git-send-email-rui.teng@linux.vnet.ibm.com> (raw)
It is a requirement from the perf todo list:
The feature tests should be performed only when a file that needs those tests,
or at least only when some .c or .h file will be rebuilt
An initial step would be for 'make install-doc' not to run the feature tests,
there it is not needed at all.
By adding 'install-doc' to the NON_CONFIG_TARGETS, it will skip running the
feature tests for such target. The Auto-detecting system features list will
not be displayed:
$ make install-doc
BUILD: Doing 'make -j2' parallel build
SUBDIR Documentation
make[2]: Nothing to be done for 'install'.
Signed-off-by: Rui Teng <rui.teng@linux.vnet.ibm.com>
---
tools/perf/Makefile.perf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index 2d90875..9c1dac6 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -165,7 +165,7 @@ SUBCMD_DIR = $(srctree)/tools/lib/subcmd/
# non-config cases
config := 1
-NON_CONFIG_TARGETS := clean TAGS tags cscope help
+NON_CONFIG_TARGETS := clean TAGS tags cscope help install-doc
ifdef MAKECMDGOALS
ifeq ($(filter-out $(NON_CONFIG_TARGETS),$(MAKECMDGOALS)),)
--
2.7.4
next reply other threads:[~2016-08-10 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 8:49 Rui Teng [this message]
2016-08-15 16:39 ` Arnaldo Carvalho de Melo
2016-08-24 9:24 ` [tip:perf/core] perf tools: " tip-bot for Rui Teng
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=1470818948-17784-1-git-send-email-rui.teng@linux.vnet.ibm.com \
--to=rui.teng@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®