From: Jonathan Corbet <corbet@lwn.net>
To: Ross Zwisler <zwisler@chromium.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Ross Zwisler <zwisler@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH] docs: ftrace: always use canonical ftrace path
Date: Thu, 26 Jan 2023 11:28:38 -0700 [thread overview]
Message-ID: <87a6259mll.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230125213251.2013791-1-zwisler@google.com>
Ross Zwisler <zwisler@chromium.org> writes:
> The canonical location for the tracefs filesystem is at /sys/kernel/tracing.
>
> But, from Documentation/trace/ftrace.rst:
>
> Before 4.1, all ftrace tracing control files were within the debugfs
> file system, which is typically located at /sys/kernel/debug/tracing.
> For backward compatibility, when mounting the debugfs file system,
> the tracefs file system will be automatically mounted at:
>
> /sys/kernel/debug/tracing
>
> Many parts of Documentation still reference this older debugfs path, so
> let's update them to avoid confusion.
>
> Signed-off-by: Ross Zwisler <zwisler@google.com>
So this seems like a good cleanup to me. Unless somebody objects, I'll
apply it to the docs tree in the near future.
Thanks,
jon
next prev parent reply other threads:[~2023-01-26 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 21:32 [PATCH] docs: ftrace: always use canonical ftrace path Ross Zwisler
2023-01-26 18:28 ` Jonathan Corbet [this message]
2023-01-26 18:58 ` Steven Rostedt
2023-01-26 20:34 ` Steven Rostedt
2023-01-26 20:41 ` Ross Zwisler
2023-01-26 21:02 ` Steven Rostedt
2023-01-31 21:30 ` Jonathan Corbet
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=87a6259mll.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zanussi@kernel.org \
--cc=zwisler@chromium.org \
--cc=zwisler@google.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).