From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH] tools lib traceevent: Modify header to work in C++ programs
Date: Wed, 22 Aug 2012 15:47:50 +0900 [thread overview]
Message-ID: <87boi3ifs9.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1345590800.5069.17.camel@gandalf.local.home> (Steven Rostedt's message of "Tue, 21 Aug 2012 19:13:20 -0400")
Hi, Steve
On Tue, 21 Aug 2012 19:13:20 -0400, Steven Rostedt wrote:
> tools lib traceevent: Modify header to work in C++ programs
>
> Replace keyword "private" from event-parse.h to allow it to be
> used in C++ programs.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> diff --git a/tools/lib/traceevent/event-parse.h b/tools/lib/traceevent/event-parse.h
> index 5772ad8..c28713b 100644
> --- a/tools/lib/traceevent/event-parse.h
> +++ b/tools/lib/traceevent/event-parse.h
> @@ -49,7 +49,7 @@ struct pevent_record {
> int cpu;
> int ref_count;
> int locked; /* Do not free, even if ref_count is zero */
> - void *private;
> + void *r_private;
This r_ (and p_) prefix make it inconsistent with others. How about
simply using 'priv' instead?
Thanks,
Namhyung
> #if DEBUG_RECORD
> struct pevent_record *prev;
> struct pevent_record *next;
> @@ -106,7 +106,7 @@ struct plugin_option {
> char *plugin_alias;
> char *description;
> char *value;
> - void *private;
> + void *p_private;
> int set;
> };
>
next prev parent reply other threads:[~2012-08-22 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 23:13 Steven Rostedt
2012-08-22 6:47 ` Namhyung Kim [this message]
2012-08-23 15:17 ` Steven Rostedt
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=87boi3ifs9.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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