From: Namhyung Kim <namhyung@kernel.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Minor perf build fixes
Date: Tue, 09 Jul 2013 14:22:36 +0900 [thread overview]
Message-ID: <87zjtwxq77.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1373019377-12741-1-git-send-email-artagnon@gmail.com> (Ramkumar Ramachandra's message of "Fri, 5 Jul 2013 15:46:13 +0530")
Hi Ramkumar,
On Fri, 5 Jul 2013 15:46:13 +0530, Ramkumar Ramachandra wrote:
> Hi,
>
> After Namhyung's review of the first iteration, I realized that I'd
> made a few mistakes. This iteration should be much better.
>
> [1/4] is the same as before.
>
> [2/4] is new, and is used in [4/4].
>
> [3/4] introduces a util/perf-perl.h to include <perl.h> with #pragma
> statements, hence eliminating duplication. It then updates Context.xs
> and trace-event-perl.c to use this new header.
I prefer the name being "perl.h" and use #include_next as we include the
'util' directory in the compiler search path.
Other than that, the change looks good to me.
>
> Also, notice that feature-tests.mak has not been touched in this
> iteration: the Perl check passes without needing the #pragma
> statements (although I'm not sure why exactly).
I guess it's because FLAGS_PERL_EMBED doesn't contain the usual perf
CFLAGS which has -Werror.
Thanks,
Namhyung
>
> Thanks.
>
> Ramkumar Ramachandra (4):
> perf/Makefile: do not open-code shell-sq
> perf/Perf-Trace-Util: fix broken include in Context.xs
> perf: squelch warnings from perl.h to compile-pass
> perf/Perf-Trace-Util: regenerate Context.c
>
> tools/perf/Makefile | 2 +-
> tools/perf/config/Makefile | 23 ++-
> tools/perf/scripts/perl/Perf-Trace-Util/Context.c | 215 +++++++++++++++++----
> tools/perf/scripts/perl/Perf-Trace-Util/Context.xs | 6 +-
> tools/perf/util/perf-perl.h | 10 +
> .../perf/util/scripting-engines/trace-event-perl.c | 2 +-
> 6 files changed, 199 insertions(+), 59 deletions(-)
> create mode 100644 tools/perf/util/perf-perl.h
next prev parent reply other threads:[~2013-07-09 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 10:16 Ramkumar Ramachandra
2013-07-05 10:16 ` [PATCH v2 1/4] perf/Makefile: do not open-code shell-sq Ramkumar Ramachandra
2013-07-05 10:16 ` [PATCH v2 2/4] perf/Perf-Trace-Util: fix broken include in Context.xs Ramkumar Ramachandra
2013-07-05 10:16 ` [PATCH v2 3/4] perf: squelch warnings from perl.h to compile-pass Ramkumar Ramachandra
2013-07-05 10:16 ` [PATCH v2 4/4] perf/Perf-Trace-Util: regenerate Context.c Ramkumar Ramachandra
2013-07-09 5:22 ` Namhyung Kim [this message]
2013-07-09 8:51 ` [PATCH v2 0/4] Minor perf build fixes Ramkumar Ramachandra
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=87zjtwxq77.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.kernel.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®