linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] tools/lib/traceevent: Rename input arguments of libtraceevent APIs from pevent to tep
Date: Wed, 27 Mar 2019 11:06:13 -0400	[thread overview]
Message-ID: <20190327110613.354d11e7@gandalf.local.home> (raw)
In-Reply-To: <20190327141946.4353-3-tstoyanov@vmware.com>

On Wed, 27 Mar 2019 16:19:43 +0200
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:

> This patch renames "struct tep_handle *pevent" input arguments of libtraceevent
> APIs to "struct tep_handle *tep". This makes the API consistent with the chosen
> naming convention: tep (trace event parser), instead of the old pevent.
> 
> Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> ---
>  tools/lib/traceevent/event-parse-api.c     | 132 +++---
>  tools/lib/traceevent/event-parse-local.h   |   6 +-
>  tools/lib/traceevent/event-parse.c         | 473 ++++++++++-----------
>  tools/lib/traceevent/event-parse.h         | 120 +++---
>  tools/lib/traceevent/event-plugin.c        |   8 +-
>  tools/lib/traceevent/parse-filter.c        |   8 +-
>  tools/lib/traceevent/plugin_cfg80211.c     |   8 +-
>  tools/lib/traceevent/plugin_function.c     |   8 +-
>  tools/lib/traceevent/plugin_hrtimer.c      |  12 +-
>  tools/lib/traceevent/plugin_jbd2.c         |  12 +-
>  tools/lib/traceevent/plugin_kmem.c         |  28 +-
>  tools/lib/traceevent/plugin_kvm.c          |  44 +-
>  tools/lib/traceevent/plugin_mac80211.c     |   8 +-
>  tools/lib/traceevent/plugin_sched_switch.c |  16 +-
>  tools/lib/traceevent/plugin_scsi.c         |   8 +-
>  tools/lib/traceevent/plugin_xen.c          |   8 +-
>  16 files changed, 449 insertions(+), 450 deletions(-)
> 
>

Can you rebase the rest of these patches off of my repo:

 git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git

 Branch: tip/perf/core

Thanks,

-- Steve

  reply	other threads:[~2019-03-27 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 14:19 [PATCH v2 0/5] Cleanup traceevent API and make it more consistent Tzvetomir Stoyanov
2019-03-27 14:19 ` [PATCH v2 1/5] tools/perf,tools/lib/traceevent: Make traceevent APIs " Tzvetomir Stoyanov
2019-03-27 14:41   ` Steven Rostedt
2019-03-27 14:19 ` [PATCH v2 2/5] tools/lib/traceevent: Rename input arguments of libtraceevent APIs from pevent to tep Tzvetomir Stoyanov
2019-03-27 15:06   ` Steven Rostedt [this message]
2019-03-27 14:19 ` [PATCH v2 3/5] tools/perf,tools/lib/traceevent: Rename "pevent" member of struct tep_event to "tep" Tzvetomir Stoyanov
2019-03-27 14:19 ` [PATCH v2 4/5] tools/perf,tools/lib/traceevent: Rename "pevent" member of struct tep_event_filter " Tzvetomir Stoyanov
2019-03-27 14:19 ` [PATCH v2 5/5] tools/lib/traceevent: Rename input arguments and local variables of libtraceevent from pevent to tep Tzvetomir Stoyanov

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=20190327110613.354d11e7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=tstoyanov@vmware.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).