Re: [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet

[Kent Overstreet]

On Tue, May 07, 2013 at 01:46:42PM -0700, Dave Hansen wrote:
> Michal, I figure you're the most logical person for these to go
> through.
> 
> 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.
> 
> ---
> 
> 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.

Yes, please!

I'm sure there's more that could be done but, like you said, it's a
start - and a significant one.

Any chance this could go in sooner than later? I spend way too much time
hunting down options in kernel hacking and I spend enough time in that
menu that I should have the damn thing memorized by now.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/