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] Remove tracefs_get_tracing_dir() API
Date: Tue, 22 Dec 2020 07:06:44 +0200	[thread overview]
Message-ID: <20201222050646.375340-1-tz.stoyanov@gmail.com> (raw)

The two APIs to get the tracefs mount point
tracefs_get_tracing_dir() and tracefs_find_tracing_dir()
are replaced by single one, tracefs_tracing_dir().

Tzvetomir Stoyanov (VMware) (2):
  trace-cmd: Rename tracefs_get_tracing_dir() to tracefs_tracing_dir()
  trace-cmd: Use tracefs_tracing_dir() instead of
    tracefs_find_tracing_dir()

 include/tracefs/tracefs.h            |  7 ++-----
 kernel-shark/src/KsCaptureDialog.cpp |  4 ++--
 lib/trace-cmd/trace-output.c         |  7 +++++--
 lib/trace-cmd/trace-recorder.c       |  6 +++---
 lib/tracefs/include/tracefs-local.h  |  2 ++
 lib/tracefs/tracefs-events.c         |  6 +++---
 lib/tracefs/tracefs-instance.c       |  2 +-
 lib/tracefs/tracefs-utils.c          | 14 +++++++-------
 tracecmd/trace-check-events.c        |  2 +-
 tracecmd/trace-record.c              | 19 ++++++++++++-------
 utest/tracefs-utest.c                | 23 +++++++----------------
 11 files changed, 45 insertions(+), 47 deletions(-)

-- 
2.28.0


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  5:06 Tzvetomir Stoyanov (VMware) [this message]
2020-12-22  5:06 ` [PATCH 1/2] trace-cmd: Rename tracefs_get_tracing_dir() to tracefs_tracing_dir() Tzvetomir Stoyanov (VMware)
2020-12-22  5:06 ` [PATCH 2/2] trace-cmd: Use tracefs_tracing_dir() instead of tracefs_find_tracing_dir() 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=20201222050646.375340-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).