From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] trace-cmd: Use tracefs_tracing_dir() instead of tracefs_find_tracing_dir()
Date: Mon, 21 Dec 2020 10:15:58 -0500 [thread overview]
Message-ID: <20201221101558.6fa01b6e@gandalf.local.home> (raw)
In-Reply-To: <20201221065103.199777-1-tz.stoyanov@gmail.com>
On Mon, 21 Dec 2020 08:51:03 +0200
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> The tracefs_find_tracing_dir() and tracefs_tracing_dir() are
> consolidated. All usage of tracefs_find_tracing_dir() are replaced with
> calls to tracefs_tracing_dir().
>
Hmm, I appear to be missing the patch that renames
tracefs_get_tracing_dir() to tracefs_tracing_dir() for trace-cmd.
I have it for libtracefs.
-- Steve
next prev parent reply other threads:[~2020-12-21 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 6:51 [PATCH] trace-cmd: Use tracefs_tracing_dir() instead of tracefs_find_tracing_dir() Tzvetomir Stoyanov (VMware)
2020-12-21 15:15 ` Steven Rostedt [this message]
2020-12-22 5:06 ` 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=20201221101558.6fa01b6e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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).