From: Namhyung Kim <namhyung.kim@lge.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 2/2] perf tools: Always try to build libtraceevent
Date: Wed, 23 May 2012 10:13:55 +0900 [thread overview]
Message-ID: <87k4031yy4.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20120522153648.GD19247@infradead.org> (Arnaldo Carvalho de Melo's message of "Tue, 22 May 2012 12:36:48 -0300")
Hi,
On Tue, 22 May 2012 12:36:48 -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, May 22, 2012 at 06:03:54PM +0900, Namhyung Kim escreveu:
>> While at it, silence annoying directory change messages.
>
> Applied, have you seen these?
>
> make[1]: Entering directory `/home/git/linux/tools/lib/traceevent'
> make[2]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
> make[2]: `libtraceevent.a' is up to date.
Yes, but I didn't know how to handle them properly. And the first line
looks like a bug of QUIET_SUBDIR stuff. Did you build it out of the
kernel tree?
Thanks,
Namhyung
next prev parent reply other threads:[~2012-05-23 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 9:03 [PATCH 1/2] perf tools: Rename libparsevent to libtraceevent in Makefile Namhyung Kim
2012-05-22 9:03 ` [PATCH 2/2] perf tools: Always try to build libtraceevent Namhyung Kim
2012-05-22 15:36 ` Arnaldo Carvalho de Melo
2012-05-23 1:13 ` Namhyung Kim [this message]
2012-05-23 1:43 ` Arnaldo Carvalho de Melo
2012-05-23 15:23 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-05-23 15:23 ` [tip:perf/core] perf tools: Rename libparsevent to libtraceevent in Makefile tip-bot for Namhyung Kim
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=87k4031yy4.fsf@sejong.aot.lge.com \
--to=namhyung.kim@lge.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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