From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/7] move debugfs to filesystems menu (fs/Kconfig)
Date: Mon, 17 Dec 2012 18:21:30 -0800 [thread overview]
Message-ID: <20121218022130.GA16839@kroah.com> (raw)
In-Reply-To: <20121217182207.4CF51258@kernel.stglabs.ibm.com>
On Mon, Dec 17, 2012 at 01:22:07PM -0500, Dave Hansen wrote:
>
> debugfs may have started out as a kernel hacking kind of option. But,
> today, it is an integral part of lots of facilities like tracing that
> are far from kernel hacking. Let's move it out of the very cluttered
> "Kernel Hacking" menu and but it next to its real family: other
> filesystems like sysfs, configfs, or /proc.
>
> Also, "Debug filesystem" sounds like a debugging option _for_
> filesystems code, not a filesystem for debugging. We also never call
> it "the debug filesystem." We always say "debugfs", so reflect the
> fact that we _call_ it debugfs in the menu text.
>
> Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2012-12-18 2:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 18:22 [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2012-12-17 18:22 ` Dave Hansen
2012-12-17 18:22 ` [PATCH 1/7] move debugfs to filesystems menu (fs/Kconfig) Dave Hansen
2012-12-18 2:21 ` Greg KH [this message]
2012-12-18 2:21 ` Greg KH
2012-12-17 18:22 ` [PATCH 2/7] consolidate per-arch stack overflow debugging options Dave Hansen
2012-12-17 18:22 ` [PATCH 3/7] order memory debugging Kconfig options Dave Hansen
2012-12-17 18:22 ` [PATCH 4/7] consolidate RCU " Dave Hansen
2012-12-17 18:22 ` Dave Hansen
2012-12-17 18:22 ` [PATCH 5/7] consolidate runtime testing configs Dave Hansen
2012-12-17 18:22 ` Dave Hansen
2012-12-17 18:22 ` [PATCH 6/7] consolidate compilation option configs Dave Hansen
2012-12-17 18:22 ` [PATCH 7/7] group locking debugging options Dave Hansen
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=20121218022130.GA16839@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).