From: Matthew Garrett <mjg@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Len Brown <lenb@kernel.org>, Cong Wang <amwang@redhat.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, Takao Indoh <tindoh@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-doc@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [Patch] acpi: introduce "acpi_addr=" parameter for kdump
Date: Wed, 23 Mar 2011 17:40:15 +0000 [thread overview]
Message-ID: <20110323174015.GA6953@srcf.ucam.org> (raw)
In-Reply-To: <m1lj06zc4u.fsf@fess.ebiederm.org>
On Tue, Mar 22, 2011 at 09:36:33PM -0700, Eric W. Biederman wrote:
> Len Brown <lenb@kernel.org> writes:
> > This should also be [KEXEC], and the code should be #ifdef CONFIG_KEXEC
> > so that sane people can exclude it from their kernels.
>
> So far sane people don't use EFI on x86 so that is easy enough.
This year's Lenovos and Dells (at least) boot EFI by default. While I'd
love to see everybody involved in EFI be relocated to a single small
island without any ability to communicate with the rest of the world,
it's unfortunately a reality and we have to deal with it.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2011-03-23 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:10 [Patch] acpi: introduce "acpi_addr=" parameter for kdump Amerigo Wang
2011-03-10 14:39 ` Vivek Goyal
2011-03-10 15:59 ` Takao Indoh
2011-03-10 17:50 ` Eric W. Biederman
2011-03-10 18:50 ` Matthew Garrett
2011-03-21 6:40 ` Cong Wang
2011-03-21 8:05 ` Eric W. Biederman
2011-03-21 15:56 ` Vivek Goyal
2011-03-22 6:31 ` Cong Wang
2011-03-10 16:26 ` Randy Dunlap
2011-03-21 6:43 ` Cong Wang
2011-03-23 4:28 ` Len Brown
2011-03-23 4:36 ` Eric W. Biederman
2011-03-23 17:40 ` Matthew Garrett [this message]
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=20110323174015.GA6953@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=amwang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tindoh@redhat.com \
--cc=vgoyal@redhat.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 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).