From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Parag Warudkar <parag.warudkar@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"akpm@osdl.org" <akpm@osdl.org>,
Peter Zijlstra <peterz@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED
Date: Mon, 5 May 2008 20:42:35 +0200 [thread overview]
Message-ID: <20080505184235.GD22332@elte.hu> (raw)
In-Reply-To: <20080505182427.GA2025@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> > This is a many years old kconfig bug that is frequently hacked
> > around in distro kernel packages but which has been ignored upstream
> > - i've attached Fedora's nonint_oldconfig patch from Dave Jones
> > below. (maybe Arjan wrote it originally?)
>
> In latest kbuild.git I've added a new feature.
>
> make K=.config alldefconfig
>
> would give you eaxtly what you request here. K= is used to say where
> to locate the base-configuration.
great, thanks Sam!
( how hard would it be to fix the "make oldconfig < /dev/null" infinit
loop bug btw? I've got this method in a number of scripts of mine and
it's an intuitive thing to type anyway, i think users would like it if
it Just Worked. )
> redhat has the added possibility to list new symbols.
> This is not yet included in mainline.
> Not that it is difficult - I just need to decide where/how to do it.
the idea of that is this: distro maintainers dont just want to accept
new options blindly, they want to make a conscious decision on what
default to use. So the Fedora rpm builds will bail out with an error if
a config option has not been provided with a default by the pre-cooked
configs that are in the SRPM.
In practice distro maintainers will pick the upstream default 99% of the
time, this is a mechanism to be 'aware' of what is happening upstream,
via a non-interactive build method. Would be cool to merge this feature
upstream too, in a clean way.
Ingo
next prev parent reply other threads:[~2008-05-05 18:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 0:42 [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED Parag Warudkar
2008-05-04 9:24 ` Ingo Molnar
2008-05-05 15:14 ` Parag Warudkar
2008-05-05 17:15 ` Ingo Molnar
2008-05-05 18:24 ` Sam Ravnborg
2008-05-05 18:36 ` Sergio Luis
2008-05-05 18:45 ` Ingo Molnar
2008-05-05 19:49 ` [PATCH] kconfig: add support for stdin (make K=- ...) Sam Ravnborg
2008-05-06 3:51 ` Oleg Verych
2008-05-05 19:05 ` [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED Sam Ravnborg
2008-05-05 18:42 ` Ingo Molnar [this message]
2008-05-05 19:01 ` Sam Ravnborg
2008-05-05 19:56 ` Arjan van de Ven
2008-05-05 20:27 ` Ingo Molnar
2008-05-05 20:48 ` Linus Torvalds
2008-05-05 21:05 ` Ingo Molnar
2008-05-05 21:40 ` Parag Warudkar
2008-05-25 19:30 ` Roman Zippel
2008-05-05 17:21 ` Ingo Molnar
2008-05-05 17:33 ` Jesse Barnes
2008-05-05 18:36 ` Ingo Molnar
2008-05-05 21:36 ` Parag Warudkar
2008-05-05 21:49 ` Ingo Molnar
2008-05-06 0:38 ` Ingo Molnar
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=20080505184235.GD22332@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox