From: Greg KH <greg@kroah.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
GeunSik Lim <leemgs1@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
trivial@kernel.org, balagi@justmail.de, bgamari@gmail.com,
Ingo Molnar <mingo@elte.hu>,
inaky.perez-gonzalez@intel.com
Subject: Re: [RFC PATCH]debugfs:Fix terminology inconsistency of dir name to mount debugfs filesystem.
Date: Wed, 27 May 2009 12:13:10 -0700 [thread overview]
Message-ID: <20090527191310.GA466@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0905271418290.17378@gandalf.stny.rr.com>
On Wed, May 27, 2009 at 02:22:37PM -0400, Steven Rostedt wrote:
>
> On Wed, 27 May 2009, Jaswinder Singh Rajput wrote:
>
> > Hello Steve,
> >
> > On Tue, 2009-05-26 at 22:38 -0400, Steven Rostedt wrote:
> >
> > > If you look in Documentation/trace/ftrace.txt I have:
> > >
> > > ===
> > > To mount the debugfs system:
> > >
> > > # mkdir /debug
> > > # mount -t debugfs nodev /debug
> > >
> > > ( Note: it is more common to mount at /sys/kernel/debug, but for
> > > simplicity this document will use /debug)
> > > ===
> > >
> >
> > Please standardize Documentation/trace/ftrace.txt and avoid confusion to
> > users:
> >
> > ===
> > To mount the debugfs system:
> >
> > # mount -t debugfs nodev /sys/kernel/debug
> > ===
>
> I really don't want to do that. Then I would need to show
>
> # echo function_graph > /sys/kernel/debug/current_trace
>
> Which I really do not like. I state that the common place to mount it is
> in /sys/kernel/debug, But my examples are much easier to understand if
> I just do: # echo function_graph > /debug/current_trace
It's not just the "common" place, it is the DOCUMENTED PLACE.
I'm sorry you have to type a long path, perhaps you wish to invest in a
tab key for auto-completion :)
Again, distros already mount debugfs at this location, please don't
confuse people just because you are annoyed at the length of the path.
thanks,
greg k-h
next prev parent reply other threads:[~2009-05-27 19:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 5:19 [RFC PATCH]debugfs:Fix terminology inconsistency of dir name to mount debugfs filesystem GeunSik Lim
2009-05-26 19:50 ` Iñaky Pérez-González
2009-05-26 20:44 ` Steven Rostedt
2009-05-26 20:54 ` Greg KH
2009-05-26 21:15 ` Steven Rostedt
2009-05-26 22:14 ` Greg KH
2009-05-27 2:24 ` GeunSik Lim
2009-05-27 2:38 ` Steven Rostedt
2009-05-27 5:30 ` GeunSik Lim
2009-05-27 5:50 ` Jaswinder Singh Rajput
2009-05-27 18:22 ` Steven Rostedt
2009-05-27 19:13 ` Greg KH [this message]
2009-05-28 13:45 ` Steven Rostedt
2009-05-28 21:41 ` Greg KH
2009-05-28 22:17 ` GeunSik Lim
2009-05-29 16:05 ` [RFC V2 " GeunSik Lim
2009-05-29 16:27 ` Steven Rostedt
2009-05-29 16:33 ` Steven Rostedt
2009-05-29 16:35 ` Steven Rostedt
2009-05-29 16:48 ` Steven Rostedt
2009-05-30 1:43 ` GeunSik Lim
2009-05-30 2:28 ` Steven Rostedt
2009-05-30 9:38 ` GeunSik Lim
2009-05-30 11:21 ` GeunSik Lim
2009-05-30 13:44 ` Steven Rostedt
2009-05-30 15:17 ` GeunSik Lim
2009-05-30 13:36 ` Steven Rostedt
2009-05-31 3:04 ` [RFC V3 " GeunSik Lim
2009-06-02 6:01 ` [PATCH V1]debugfs:Fix " GeunSik Lim
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=20090527191310.GA466@kroah.com \
--to=greg@kroah.com \
--cc=balagi@justmail.de \
--cc=bgamari@gmail.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=jaswinder@kernel.org \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=trivial@kernel.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