From: Michael Tokarev <mjt@tls.msk.ru>
To: Valdis.Kletnieks@vt.edu
Cc: Jeff Garzik <jeff@garzik.org>, Grant Coady <gcoady.lk@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-mm1 make oldconfig missed SATA
Date: Mon, 25 Sep 2006 13:25:54 +0400 [thread overview]
Message-ID: <4517A0A2.5020209@tls.msk.ru> (raw)
In-Reply-To: <200609250038.k8P0cEX1017825@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Sun, 24 Sep 2006 20:12:10 EDT, Jeff Garzik said:
>> Grant Coady wrote:
>>> 2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
>
>>> the new libata screen, caught me out -- this may be an issue for 2.6.19
>>> upgraders that a quick make oldconfig rebuild will fail to boot?
>> The symbols changed. No facility for upgrading .config symbols...
>> people who config their own kernels are expected to handle such things...
>
> I remember getting hit with this several times in the last few -mm's as I
> did bisecting and kept crossing over the patch that did that. Fortunately,
> 'make oldconfig' was nice enough to keep me honest and prompt me for the new
> symbol names.
>
> What the Kbuild system *could* use is, for the end of 'make oldconfig', a
> report like this for 'y' or 'm' symbols that have evaporated:
>
> The following enabled symbols found in the .config were not defined in any Kconfig file:
> CONFIG_FROOBY
> CONFIG_DEBUG_FROOBY
>
> So people aren't totally mystified Admittedly, I've only gotten bit by
> silently dissapearing symbols 4-5 times since 2.5.55 or so, but the times
> it happened it would have been nice to know....
It already does that, but prints them in the beginning, not after config.
Try make silentoldconfig and see the first screen of warnings when it will
ask the first question.
/mjt
next prev parent reply other threads:[~2006-09-25 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 23:00 Grant Coady
2006-09-25 0:12 ` Jeff Garzik
2006-09-25 0:38 ` Valdis.Kletnieks
2006-09-25 9:25 ` Michael Tokarev [this message]
2006-09-25 13:31 ` Valdis.Kletnieks
2006-09-25 1:24 ` Grant Coady
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=4517A0A2.5020209@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=Valdis.Kletnieks@vt.edu \
--cc=gcoady.lk@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®