From: Namhyung Kim <namhyung@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] perf: clean target should do clean for lib/traceevent too
Date: Thu, 06 Sep 2012 10:16:57 +0900 [thread overview]
Message-ID: <87sjawc5me.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1346892816-61779-1-git-send-email-dsahern@gmail.com> (David Ahern's message of "Wed, 5 Sep 2012 18:53:36 -0600")
On Wed, 5 Sep 2012 18:53:36 -0600, David Ahern wrote:
> It's built as part of perf, so it should be cleaned too.
>
> Signed-off-by: David Ahern <dsahern@gmail.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
Tested-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> tools/perf/Makefile | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/Makefile b/tools/perf/Makefile
> index 90d8e09..e7e62b2 100644
> --- a/tools/perf/Makefile
> +++ b/tools/perf/Makefile
> @@ -921,6 +921,9 @@ $(LIB_FILE): $(LIB_OBJS)
> $(LIBTRACEEVENT):
> $(QUIET_SUBDIR0)$(TRACE_EVENT_DIR) $(QUIET_SUBDIR1) O=$(OUTPUT) libtraceevent.a
>
> +$(LIBTRACEEVENT)-clean:
> + $(QUIET_SUBDIR0)$(TRACE_EVENT_DIR) $(QUIET_SUBDIR1) O=$(OUTPUT) clean
> +
> help:
> @echo 'Perf make targets:'
> @echo ' doc - make *all* documentation (see below)'
> @@ -1060,7 +1063,7 @@ quick-install-html:
>
> ### Cleaning rules
>
> -clean:
> +clean: $(LIBTRACEEVENT)-clean
> $(RM) $(LIB_OBJS) $(BUILTIN_OBJS) $(LIB_FILE) $(OUTPUT)perf-archive $(OUTPUT)perf.o $(LANG_BINDINGS)
> $(RM) $(ALL_PROGRAMS) perf
> $(RM) *.spec *.pyc *.pyo */*.pyc */*.pyo $(OUTPUT)common-cmds.h TAGS tags cscope*
next prev parent reply other threads:[~2012-09-06 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 0:53 David Ahern
2012-09-06 1:16 ` Namhyung Kim [this message]
2012-09-07 6:11 ` [tip:perf/core] perf tools: Clean target should do clean for lib/ traceevent too tip-bot for David Ahern
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=87sjawc5me.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
Powered by JetHome