From: Steven Rostedt <rostedt@goodmis.org>
To: tzvmware@gmail.com
Cc: linux-trace-devel@vger.kernel.org,
Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: Re: [PATCH v2] tools/lib/traceevent, tools/perf: Move struct tep_handler definition in a local header file
Date: Fri, 5 Oct 2018 17:13:47 -0400 [thread overview]
Message-ID: <20181005171347.5e5f9341@gandalf.local.home> (raw)
In-Reply-To: <20181005123125.7cbcaf84@gandalf.local.home>
On Fri, 5 Oct 2018 12:31:25 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > +/**
> > + * tep_get_events_count - get the number of defined events
> > + * @pevent: a handle to the tep_handle
> > + *
> > + * This returns number of elements in event array
> > + * If @pevent is NULL, 0 is returned.
>
> Here too with the pevent/tep.
>
> > + */
> > +int tep_get_events_count(struct tep_handle *tep)
> > +{
> > + if(tep)
> > + return tep->nr_events;
> > + return 0;
> > +}
> > +
> > +/**
> > + * tep_set_flag - set event parser flag
> > + * @pevent: a handle to the tep_handle
> > + * @flag: flag, or combination of flags to be set
> > + * can be any combination from enum tep_flag
>
> Ditto.
I never committed these changes :-p
So they are not updated. Please fix this on v3.
Thanks!
-- Steve
next prev parent reply other threads:[~2018-10-06 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181005091709.2bd7abe8@gandalf.local.home>
2018-10-05 13:31 ` [PATCH v2] tools/lib/traceevent, tools/perf: Move struct tep_handler definition in a local header file tzvmware
2018-10-05 16:31 ` Steven Rostedt
2018-10-05 21:13 ` Steven Rostedt [this message]
2018-10-08 12:55 ` [PATCH v3] " tzvmware
2018-10-08 19:52 ` Steven Rostedt
2018-10-03 0:05 [PATCH] " Steven Rostedt
2018-10-05 12:53 ` [PATCH v2] " tzvmware
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=20181005171347.5e5f9341@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.com \
--cc=tzvmware@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).