From: Dave Jones <davej@redhat.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet
Date: Fri, 14 Dec 2012 14:35:53 -0500 [thread overview]
Message-ID: <20121214193553.GA2835@redhat.com> (raw)
In-Reply-To: <20121214184200.8EC5168B@kernel.stglabs.ibm.com>
On Fri, Dec 14, 2012 at 01:42:00PM -0500, Dave Hansen wrote:
> I think the "Kernel Hacking" menu has gotten a bit out of hand. It
> is over 120 lines long on my system with everything enabled and
> options are scattered around it haphazardly.
>
> http://sr71.net/~dave/linux/kconfig-horror.png
>
> Let's try to introduce some sanity.
Nice. Perhaps as a follow-on patch, split up the Kconfig.debug into
a handful of files too ?
Thinking it might help prevent things getting so messed up again
when people start adding more options.
Dave
prev parent reply other threads:[~2012-12-14 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 18:42 [RFC][PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 1/7] move debugfs to filesystems menu (fs/Kconfig) Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 2/7] consolidate per-arch stack overflow debugging options Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 3/7] order memory debugging Kconfig options Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 4/7] consolidate RCU " Dave Hansen
2013-01-07 16:22 ` Paul E. McKenney
2012-12-14 18:42 ` [RFC][PATCH 5/7] consolidate runtime testing configs Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 6/7] consolidate compilation option configs Dave Hansen
2012-12-14 18:42 ` [RFC][PATCH 7/7] group locking debugging options Dave Hansen
2012-12-14 19:35 ` Dave Jones [this message]
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=20121214193553.GA2835@redhat.com \
--to=davej@redhat.com \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.