From: Dave Jones <davej@redhat.com>
To: Kent Overstreet <koverstreet@google.com>
Cc: Dave Hansen <dave@sr71.net>,
mmarek@suse.cz, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, tj@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet
Date: Thu, 9 May 2013 14:12:54 -0400 [thread overview]
Message-ID: <20130509181254.GA20844@redhat.com> (raw)
In-Reply-To: <20130509173130.GA17021@moria.home.lan>
On Thu, May 09, 2013 at 10:31:30AM -0700, Kent Overstreet wrote:
> > 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.
> >
> 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.
+1. I was concerned that Dave had dropped this since the first time
it got posted a few months ago. That stuff is long overdue a cleanup.
Dave
next prev parent reply other threads:[~2013-05-09 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 20:46 [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2013-05-07 20:46 ` [PATCH 1/7] consolidate per-arch stack overflow debugging options Dave Hansen
2013-05-07 22:53 ` James Hogan
2013-05-08 0:01 ` Dave Hansen
2013-05-07 20:46 ` [PATCH 2/7] order memory debugging Kconfig options Dave Hansen
2013-05-07 20:46 ` [PATCH 3/7] consolidate runtime testing configs Dave Hansen
2013-05-07 20:46 ` [PATCH 4/7] consolidate compilation option configs Dave Hansen
2013-05-07 20:46 ` [PATCH 5/7] group locking debugging options Dave Hansen
2013-05-07 20:46 ` [PATCH 6/7] kconfig: consolidate printk options Dave Hansen
2013-05-07 20:46 ` [PATCH 7/7] hang and lockup detection menu Dave Hansen
2013-05-09 17:31 ` [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Kent Overstreet
2013-05-09 18:12 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-01 20:04 Dave Hansen
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=20130509181254.GA20844@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=koverstreet@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=tj@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.