From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Tzvetomir Stoyanov <tstoyanov@vmware.com>,
Yordan Karadzhov <y.karadz@gmail.com>
Subject: [PATCH] kernelshark: Rename tracefs_get_tracing_dir() to the new tracefs_tracing_dir()
Date: Mon, 21 Dec 2020 14:24:58 -0500 [thread overview]
Message-ID: <20201221142458.5d5607c6@gandalf.local.home> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
libtracefs is renaming tracefs_get_tracing_dir() to tracefs_tracing_dir() as
there is no "tracefs_put_tracing_dir()" for this function. Since libtracefs
has not been officially released, it is fine to break API, as it is with
kernelshark v2.0 has not yet been official released that uses the old API.
Signen-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
src/KsCaptureDialog.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/KsCaptureDialog.cpp b/src/KsCaptureDialog.cpp
index 63fd5d6..7253ab6 100644
--- a/src/KsCaptureDialog.cpp
+++ b/src/KsCaptureDialog.cpp
@@ -26,7 +26,7 @@ extern "C" {
static inline tep_handle *local_events()
{
- return tracefs_local_events(tracefs_get_tracing_dir());
+ return tracefs_local_events(tracefs_tracing_dir());
}
/**
@@ -204,7 +204,7 @@ QStringList KsCaptureControl::_getPlugins()
QStringList pluginList;
char **all_plugins;
- all_plugins = tracefs_tracers(tracefs_get_tracing_dir());
+ all_plugins = tracefs_tracers(tracefs_tracing_dir());
if (!all_plugins)
return pluginList;
--
2.25.4
next reply other threads:[~2020-12-21 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 19:24 Steven Rostedt [this message]
2021-01-04 17:03 ` [PATCH] kernelshark: Rename tracefs_get_tracing_dir() to the new tracefs_tracing_dir() Yordan Karadzhov (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=20201221142458.5d5607c6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.com \
--cc=y.karadz@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).