All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Tony Luck <tony.luck@intel.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] don't select EFI from certain special ACPI drivers
Date: Thu, 19 Dec 2013 17:56:43 +0100	[thread overview]
Message-ID: <20131219165643.GA30382@gmail.com> (raw)
In-Reply-To: <CA+8MBb+7e03UxmJCnXSDh=8m+9LFT2R3h0v6g-wDWnn=N8vFWg@mail.gmail.com>


* Tony Luck <tony.luck@intel.com> wrote:

> On Wed, Dec 18, 2013 at 12:04 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>> On 17.12.13 at 23:34, "Luck, Tony" <tony.luck@intel.com> wrote:
> >>>  No, it hasn't. But I explicitly checked the relevant EFI=n and EFI=y
> >>> cases.
> >>
> >> I pushed your patch into my "next" tree - the robots will notice soon and
> >> send us e-mail if they find any issues.
> >
> > Thanks, Tony. I'm afraid though that fixing this only in 3.14 would
> > be a little late: Any "select" in a Kconfig results in the user not being
> > asked again when that "select" goes away, so people having got EFI
> > forcibly enabled in 3.13 and updating their configs to 3.14 would
> > then need to remember to manually disable CONFIG_EFI again (of
> > course that's already true for anyone using 3.13-rc?, but those
> > should mostly be people more knowledgeable than folks just
> > consuming final releases).
> >
> > I think it should generally be the exception to "select" options that
> > have visible prompts (i.e. are user configurable).
> 
> Ingo: Jan makes a good point that people running "make oldconfig"
> may get suckered into selecting CONFIG_EFI when they don't really
> need it.  I've not seen any complaints from the robot randconfig testers,
> so this patch is:
> 
> Acked-by: Tony Luck <tony.luck@intel.com>
> 
> Can you push it to Linus before 3.13-final releases?

Ok, agreed, I've queued it up in the tip:x86/urgent tree.

Thanks,

	Ingo

  reply	other threads:[~2013-12-19 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 14:39 [PATCH] don't select EFI from certain special ACPI drivers Jan Beulich
2013-12-16 23:04 ` Luck, Tony
2013-12-17  8:05   ` Jan Beulich
2013-12-17 22:34     ` Luck, Tony
2013-12-18  8:04       ` Jan Beulich
2013-12-18 19:13         ` Tony Luck
2013-12-19 16:56           ` Ingo Molnar [this message]
2013-12-19 20:36 ` [tip:x86/urgent] x86/efi: Don' t " tip-bot for Jan Beulich

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=20131219165643.GA30382@gmail.com \
    --to=mingo@kernel.org \
    --cc=JBeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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.