From: Ingo Molnar <mingo@elte•hu>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Andrew Morton <akpm@linux-foundation•org>,
linux-kernel@vger•kernel.org, tglx@linutronix•de,
peterz@infradead•org, torvalds@linux-foundation•org,
tytso@mit•edu, arjan@infradead•org, greg@kroah•com,
mcgrof@gmail•com, zippel@linux-m68k•org,
linux-kbuild@vger•kernel.org, sam@ravnborg•org, corbet@lwn•net,
sourcejedi.lkml@googlemail•com, andi@firstfloor•org,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org
Subject: Re: [PATCH 00/14] kconfig: streamline distro configs for testers
Date: Fri, 21 Aug 2009 18:32:20 +0200 [thread overview]
Message-ID: <20090821163220.GB20898@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0908211106560.16405@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis•org> wrote:
>
> On Fri, 21 Aug 2009, Ingo Molnar wrote:
>
> >
> > * Andrew Morton <akpm@linux-foundation•org> wrote:
> >
> > > On Thu, 20 Aug 2009 17:43:38 -0400 (EDT)
> > > Steven Rostedt <rostedt@goodmis•org> wrote:
> > >
> > > > >
> > > > > > The following patches are in:
> > > > > >
> > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> > > > > >
> > > > > > branch: kconfig
> > > > >
> > > > > Sam's been quiet lately. I suggest that you add this to linux-next
> > > > > now so people get a chance to poke at it.
> > > >
> > > > I have no means of pushing into next. Would someone like to do a pull for
> > > > me?
> > >
> > > If suitably bribed, Stephen will add you tree directly to the
> > > linux-nxt lineup.
> >
> > Yep, we always needed another kconfig maintainer (Sam's being mostly
> > busy with kbuild), and it's nice to see that Steve volunteered for
> > that job now! ;-)
>
> Sure why not?
>
> I've created a new repo:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-kconfig.git
>
> and the same changes are in the branch: for-next
Cool!
I'm wondering, what do you think about Vegard's 'warn about complex
selects' feature for kconfig which he submitted some time ago:
http://lkml.org/lkml/2008/5/4/13
That's a really sore kconfig spot we have. It's not a bug, but it
sure bites people again and again, and it would be nice to have some
built-in mechanism that gently nudges us away from complex selects.
(many of which are inadvertent or become complex after the fact)
Ingo
next prev parent reply other threads:[~2009-08-21 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090819025634.987354707@goodmis.org>
[not found] ` <20090820143025.7134930f.akpm@linux-foundation.org>
[not found] ` <alpine.DEB.2.00.0908201741370.16405@gandalf.stny.rr.com>
2009-08-20 22:13 ` [PATCH 00/14] kconfig: streamline distro configs for testers Andrew Morton
2009-08-21 13:52 ` Ingo Molnar
2009-08-21 15:08 ` Steven Rostedt
2009-08-21 16:32 ` Ingo Molnar [this message]
2009-08-21 17:39 ` Steven Rostedt
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=20090821163220.GB20898@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andi@firstfloor$(echo .)org \
--cc=arjan@infradead$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=greg@kroah$(echo .)com \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@gmail$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sam@ravnborg$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sourcejedi.lkml@googlemail$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=tytso@mit$(echo .)edu \
--cc=zippel@linux-m68k$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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