linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] Rename a few libtracecmd APIs
Date: Tue, 22 Dec 2020 14:09:49 +0200	[thread overview]
Message-ID: <20201222120951.492370-1-tz.stoyanov@gmail.com> (raw)

Renamed free_record() and tracecmd_get_pevent() APIs to have more consistent
and intuitive names.

Tzvetomir Stoyanov (VMware) (2):
  trace-cmd: Rename free_record() to tracecmd_free_record()
  trace-cmd: Rename tracecmd_get_pevent() to tracecmd_get_tep()

 include/trace-cmd/trace-cmd.h           |  4 +--
 kernel-shark/src/libkshark.c            | 20 +++++++-------
 kernel-shark/src/plugins/sched_events.c |  4 +--
 lib/trace-cmd/trace-blk-hack.c          |  2 +-
 lib/trace-cmd/trace-ftrace.c            |  4 +--
 lib/trace-cmd/trace-input.c             | 20 +++++++-------
 lib/trace-cmd/trace-output.c            |  8 +++---
 tracecmd/trace-hist.c                   |  4 +--
 tracecmd/trace-mem.c                    |  4 +--
 tracecmd/trace-profile.c                | 14 +++++-----
 tracecmd/trace-read.c                   | 36 ++++++++++++-------------
 tracecmd/trace-split.c                  | 20 +++++++-------
 tracecmd/trace-stream.c                 |  2 +-
 13 files changed, 71 insertions(+), 71 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-12-22 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 12:09 Tzvetomir Stoyanov (VMware) [this message]
2020-12-22 12:09 ` [PATCH 1/2] trace-cmd: Rename free_record() to tracecmd_free_record() Tzvetomir Stoyanov (VMware)
2020-12-22 12:09 ` [PATCH 2/2] trace-cmd: Rename tracecmd_get_pevent() to tracecmd_get_tep() Tzvetomir Stoyanov (VMware)

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=20201222120951.492370-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).