From: Matt Fleming <matt.fleming@intel.com>
To: Shea Levy <shea@shealevy.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Maarten Lankhorst <m.b.lankhorst@gmail.com>
Subject: Re: [RFC][PATCH 1/1] x86, efi: EFI boot stub config file support
Date: Thu, 31 May 2012 16:41:09 +0100 [thread overview]
Message-ID: <1338478869.13028.64.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <4F690314.3080601@shealevy.com>
On Tue, 2012-03-20 at 18:22 -0400, Shea Levy wrote:
> On 03/18/2012 11:49 AM, Shea Levy wrote:
> > On 3/18/12 11:45 AM, Shea Levy wrote:
> >> Hello,
> >>
> >> Inlined is a patch to have the kernel read its parameters from a
> >> config file when booted via the EFI boot stub without any parameters
> >> passed. This patch roughly follows the plan I discussed when
> >> proposing this idea, except now the file is found relative to the
> >> location of the bzImage and there is no additional check to see if
> >> image->parent_handle is NULL (despite the spec saying it will be NULL
> >> when the image was loaded by the firmware itself, it was never NULL
> >> on any of the systems I tested).
> >>
> >> Cheers,
> >> Shea Levy
>
> I haven't yet gotten a reply to this, should I wait until after the
> merge window and resubmit it then?
I'm wondering what use case you're catering for here that can't be
handled with efibootmgr? What problem does this patch fix?
next prev parent reply other threads:[~2012-05-31 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 15:45 Shea Levy
2012-03-18 15:49 ` Shea Levy
2012-03-20 22:22 ` Shea Levy
2012-03-20 22:24 ` H. Peter Anvin
2012-05-31 15:41 ` Matt Fleming [this message]
2012-06-02 18:32 ` Shea Levy
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=1338478869.13028.64.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.b.lankhorst@gmail.com \
--cc=mingo@redhat.com \
--cc=shea@shealevy.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®