From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Ingo, no more kconfig patches
Date: Sat, 3 May 2008 23:38:22 +0200 [thread overview]
Message-ID: <20080503213822.GA24283@uranus.ravnborg.org> (raw)
In-Reply-To: <20080503212429.GT5838@cs181133002.pp.htv.fi>
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@kernel.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@vger.kernel.org and Roman Zippel in the loop.
Sam
next prev parent reply other threads:[~2008-05-03 21:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:03 [patch] input: JOYSTICK_XPAD build fix Ingo Molnar
2008-04-30 21:02 ` Dmitry Torokhov
2008-04-30 21:13 ` Ingo Molnar
2008-04-30 23:01 ` Ingo, no more kconfig patches Adrian Bunk
2008-05-01 1:17 ` Ingo Molnar
2008-05-01 1:37 ` Adrian Bunk
2008-05-01 2:06 ` Ingo Molnar
2008-05-01 2:12 ` Adrian Bunk
2008-05-01 2:52 ` Ingo Molnar
2008-05-01 11:59 ` Adrian Bunk
2008-05-03 19:14 ` Ingo Molnar
2008-05-03 19:17 ` Ingo Molnar
2008-05-03 20:24 ` Adrian Bunk
2008-05-03 21:03 ` Ingo Molnar
2008-05-03 21:24 ` Adrian Bunk
2008-05-03 21:38 ` Sam Ravnborg [this message]
2008-05-03 22:07 ` Adrian Bunk
2008-05-04 7:36 ` Sam Ravnborg
2008-05-04 7:49 ` Adrian Bunk
2008-05-03 21:52 ` Ingo Molnar
2008-05-03 22:03 ` Adrian Bunk
2008-05-04 3:54 ` Valdis.Kletnieks
2008-05-04 7:47 ` Adrian Bunk
2008-05-03 23:22 ` Thomas Gleixner
2008-05-04 0:34 ` Adrian Bunk
2008-05-03 21:17 ` Krzysztof Halasa
2008-05-03 21:47 ` Adrian Bunk
2008-05-03 22:13 ` Krzysztof Halasa
2008-05-03 22:29 ` Adrian Bunk
2008-05-03 23:37 ` Krzysztof Halasa
2008-05-04 0:49 ` Adrian Bunk
2008-05-04 12:18 ` Krzysztof Halasa
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=20080503213822.GA24283@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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