From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: Latest tip kernel(3.2-rc1-tip_cf6b3899) fails to boot on x3850x5 machine
Date: Fri, 16 Dec 2011 09:36:34 +0100 [thread overview]
Message-ID: <20111216083634.GA4170@elte.hu> (raw)
In-Reply-To: <1323980706.1984.255.camel@sbsiddha-desk.sc.intel.com>
* Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> > yes.
>
> Not quite sure if I understand the reported issue.
>
> If the old config file had CONFIG_X86_X2APIC and
> CONFIG_INTR_REMAP set, doing "make oldconfig" on the newer
> kernel is asking if I want the new CONFIG_IRQ_REMAP option to
> be set and if I say yes, then I have both CONFIG_X86_X2APIC
> and CONFIG_IRQ_REMAP set and all is well.
>
> But if I say no, then as expected CONFIG_X86_X2APIC gets
> disabled (as IRQ_REMAP is not selected).
The problem is spuriously re-asking a question that *has already
been answered by the user*, and if the user accidentally just
accepts the default, the config breaks.
We try to keep things working fine across 'make oldconfig', i.e.
if the .config worked before, it should work after a 'make
oldconfig' as well.
Thanks,
Ingo
next prev parent reply other threads:[~2011-12-16 8:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:48 Latest tip kernel(3.2-rc1-tip_cf6b3899) fails to boot on x3850x5 machine Nikunj A Dadhania
2011-12-14 13:30 ` Thomas Gleixner
2011-12-14 20:17 ` Thomas Gleixner
2011-12-14 20:35 ` Yinghai Lu
2011-12-14 20:56 ` Thomas Gleixner
2011-12-15 2:24 ` Nikunj A Dadhania
2011-12-15 2:40 ` Yinghai Lu
2011-12-15 7:19 ` Ingo Molnar
2011-12-15 19:16 ` Yinghai Lu
2011-12-15 20:25 ` Suresh Siddha
2011-12-16 3:41 ` Nikunj A Dadhania
2011-12-16 8:36 ` Ingo Molnar [this message]
2011-12-17 2:10 ` Suresh Siddha
2011-12-18 8:32 ` Ingo Molnar
2011-12-16 8:40 ` Ingo Molnar
2011-12-16 18:03 ` Yinghai Lu
2011-12-17 2:18 ` Suresh Siddha
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=20111216083634.GA4170@elte.hu \
--to=mingo@elte.hu \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.