From: David Woodhouse <dwmw2@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Gokul Caushik <caushik1@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Joe Millenbach <jmillenbach@gmail.com>
Subject: Re: bzImage 2.12
Date: Sun, 27 Jan 2013 19:10:04 +0000 [thread overview]
Message-ID: <1359313804.10797.74.camel@shinybook.infradead.org> (raw)
In-Reply-To: <510579C1.3000800@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sun, 2013-01-27 at 11:02 -0800, H. Peter Anvin wrote:
> This is intentionally a protocol only patch, which may be possible to
> push into 3.8 as an urgent patch. David, if I understand our
> discussions right it might be better to not export XLF_EFI_HANDOFF_32
> at this time?
That won't stop broken bootloaders from jumping to $handover_offset
anyway. Anyone who was daft enough to implement EFI boot stub in their
bootloader *despite* its obvious brokenness, rather than insisting on
fixing it before it could be considered usable, will still be jumping
into hyperspace. I have little sympathy for them, but I'm told we need
to care.
It'd probably be better to just mark CONFIG_EFI_STUB as 'depends on
BROKEN' for 32-bit.
Or, and perhaps this is heresy, merge the patches which bloody fix it?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-01-27 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 19:02 bzImage 2.12 H. Peter Anvin
2013-01-27 19:10 ` David Woodhouse [this message]
2013-01-27 19:19 ` H. Peter Anvin
2013-01-27 19:25 ` Matt Fleming
2013-01-27 19:38 ` Yinghai Lu
2013-01-27 19:39 ` H. Peter Anvin
2013-01-28 2:14 ` Yinghai Lu
2013-01-28 3:36 ` H. Peter Anvin
2013-01-29 3:50 ` Yinghai Lu
2013-01-29 4:22 ` Yinghai Lu
2013-01-29 19:36 ` Yinghai Lu
2013-01-27 22:08 ` David Woodhouse
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=1359313804.10797.74.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=caushik1@gmail.com \
--cc=hpa@zytor.com \
--cc=jmillenbach@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).