mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet
Date: Mon, 01 Jul 2013 13:04:40 -0700	[thread overview]
Message-ID: <20130701200440.712D8B4E@viggo.jf.intel.com> (raw)

Linus, I've tried to send these along to a couple of different
maintainers for a couple of merge windows, but so far nobody has
bitten.

--

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.  This set takes that 120 lines
down to 55 and makes it vastly easier to find some things.  It's a
start.

This set stands on its own, but there is plenty of room for follow-up
patches.  The arch-specific debug options still end up getting stuck
in the top-level "kernel hacking" menu.  OPTIMIZE_INLINING, for
instance, could obviously go in to the "compiler options" menu, but
the fact that it is defined in arch/ in a separate Kconfig file keeps
it on its own for the moment.

--

There is a fair amount of churn in the areas around these patches
so I've resolved conflicts a couple of times.  For the patches that
are almost purely code move patches, I'm doing this:

	cat foo.patch | grep '^[-+]' | perl -pe 's/^.//' | sort | uniq -c | sort -n

and watching for any non-even numbers coming out of uniq.  This
helps me make sure I'm not adding/removing code that I should not
be.

The Signed-off-by's in here look funky.  I changed employers
while working on this set, so I have signoffs from both email
addresses.  Here's the original posting:

	http://lkml.kernel.org/r/20121217182206.91AA150A@kernel.stglabs.ibm.com


             reply	other threads:[~2013-07-01 20:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 20:04 Dave Hansen [this message]
2013-07-01 20:04 ` [PATCH 1/7] consolidate per-arch stack overflow debugging options Dave Hansen
2013-07-01 20:04 ` [PATCH 2/7] order memory debugging Kconfig options Dave Hansen
2013-07-08 16:43   ` Paul E. McKenney
2013-07-01 20:04 ` [PATCH 3/7] consolidate runtime testing configs Dave Hansen
2013-07-01 20:04 ` [PATCH 4/7] consolidate compilation option configs Dave Hansen
2013-07-01 20:04 ` [PATCH 5/7] group locking debugging options Dave Hansen
2013-07-01 20:04 ` [PATCH 6/7] kconfig: consolidate printk options Dave Hansen
2013-07-01 20:04 ` [PATCH 7/7] hang and lockup detection menu Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2013-05-07 20:46 [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2013-05-09 17:31 ` Kent Overstreet
2013-05-09 18:12   ` Dave Jones
2012-12-17 18:22 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=20130701200440.712D8B4E@viggo.jf.intel.com \
    --to=dave@sr71.net \
    --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

Powered by JetHome