[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080503213822.GA24283@uranus.ravnborg.org>
Date: Sat, 3 May 2008 23:38:22 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Adrian Bunk <bunk@...nel.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Ingo, no more kconfig patches
On Sun, May 04, 2008 at 12:24:29AM +0300, Adrian Bunk wrote:
> On Sat, May 03, 2008 at 11:03:00PM +0200, Ingo Molnar wrote:
> >
> > * Adrian Bunk <bunk@...nel.org> wrote:
> >...
> > > > As Sam said it, fixing that Kconfig design bug would be "nice" - but
> > > > unfortunately the Kconfig subsystem is not actively developed
> > > > anymore.
> > >
> > > Roman is still active.
> >
> > great, does this mean we'll see fixes for select's misbehavior, along
> > the lines of Sam's suggestions?
>
> In the case of the problem here it would have turned one problem into
> another, and Roman's patch is the correct solution no matter whether
> you change the semantics of select or not.
Hi Adrian
It would be nice to know what was wrong with my suggestion.
You have done your share of kconfig patches so you have a good grip
on the problems we face.
So any input on how we can improve kconfig so we can actually provide
what people often expects or requests or need would be nice.
I have so far not done any hacking on the core of the backend of
kconfig but if I one day find more than one hour in row where I can do
some kernel stuff I may actually try it out.
And then it would be nice to have a sketch ready how to solve the issues.
I would though request you to start a new mail thread for this and
include both linux-kbuild@...r.kernel.org and Roman Zippel in the loop.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists