From: Hugh Dickins <hugh@veritas.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CONFIG_HOTPLUG_CPU: kconfig bug?
Date: Thu, 30 Aug 2007 13:40:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708301319590.32332@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708300235010.1817@scrub.home>
On Thu, 30 Aug 2007, Roman Zippel wrote:
>
> > > > > I've noticed an oddity with CONFIG_HOTPLUG_CPU in 2.6.23-rc:
> > > > > make oldconfig seems to turn it on even when nothing wants it,
> > > > > increasing kernel size by about 10k; but if you then edit the
> > > > > line out of .config and make oldconfig again, it correctly
> > > > > offers the choice and lets it be turned off after all.
>
> It's somewhat a side effect of using select and defaults, the order of the
> config symbols becomes significant for oldconfig, if you look at the
> output you'll find:
>
> Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL) (HOTPLUG_CPU) [Y/?] y
>
> this sets it to 'y'. In this case one isn't asked about it, because there
> is only one choice. The patch below avoids the setting of the value here.
Thanks for working that out: your patch certainly works for me,
and would be good to see in 2.6.23, to prevent lots of users getting
an unnecessary CONFIG_HOTPLUG_CPU forever after. I wonder what config
options this might have forced in the past.
>
> Avoid setting the value if the symbol doesn't need to be changed or can't
> be changed. Later choices may change the dependencies and thus the
> possible input range.
>
> Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
But please add a sentence to your patch description, something like:
make oldconfig from a 2.6.22 .config with CONFIG_HOTPLUG_CPU not set
was in some configurations setting CONFIG_HOTPLUG_CPU=y without asking,
even when there was no actual requirement for CONFIG_HOTPLUG_CPU.
Thanks,
Hugh
next prev parent reply other threads:[~2007-08-30 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 14:54 CONFIG_HOTPLUG_CPU: kconfig bug? Hugh Dickins
2007-08-27 17:26 ` Sam Ravnborg
2007-08-27 20:49 ` Hugh Dickins
2007-08-29 18:01 ` Sam Ravnborg
2007-08-30 3:06 ` Roman Zippel
2007-08-30 12:40 ` Hugh Dickins [this message]
2007-08-30 18:48 ` Rafael J. Wysocki
2007-08-30 21:06 ` Hugh Dickins
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=Pine.LNX.4.64.0708301319590.32332@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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