From: Daniel Kiper <daniel.kiper@oracle.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, lersek@redhat.com, leif@nuviainc.com,
pjones@redhat.com, mjg59@google.com, agraf@csgraf.de,
ilias.apalodimas@linaro.org, xypron.glpk@gmx.de,
nivedita@alum.mit.edu, James.Bottomley@hansenpartnership.com
Subject: Re: [RFC PATCH 0/3] efi: put an API version number in the PE/COFF header
Date: Thu, 20 Feb 2020 14:53:19 +0100 [thread overview]
Message-ID: <20200220135319.7rqromng7jmyc2rw@tomti.i.net-space.pl> (raw)
In-Reply-To: <20200220110649.1303-1-ardb@kernel.org>
On Thu, Feb 20, 2020 at 12:06:46PM +0100, Ard Biesheuvel wrote:
> After having added new ways to load the initrd and the mixed mode kernel,
> we will need to tell the loader about this, so it can use the new, generic
> method if supported, and fall back to the existing method(s) otherwise.
>
> This is an RFC - if there are better ways to record this in the image
> somehow, please shout.
>
> Cc: lersek@redhat.com
> Cc: leif@nuviainc.com
> Cc: pjones@redhat.com
> Cc: mjg59@google.com
> Cc: agraf@csgraf.de
> Cc: ilias.apalodimas@linaro.org
> Cc: xypron.glpk@gmx.de
> Cc: daniel.kiper@oracle.com
> Cc: nivedita@alum.mit.edu
> Cc: James.Bottomley@hansenpartnership.com
For all the patches Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>...
I hope that we will see a bootloader, GRUB preferred, implementation for
this thing soon...
Daniel
next prev parent reply other threads:[~2020-02-20 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 11:06 [RFC PATCH 0/3] efi: put an API version number in the PE/COFF header Ard Biesheuvel
2020-02-20 11:06 ` [RFC PATCH 1/3] efi/x86: Use symbolic constants in PE header instead of bare numbers Ard Biesheuvel
2020-02-20 17:28 ` Arvind Sankar
2020-02-20 17:32 ` Ard Biesheuvel
2020-02-20 18:04 ` Arvind Sankar
2020-02-20 18:11 ` Arvind Sankar
2020-02-20 18:14 ` Ard Biesheuvel
2020-02-20 19:33 ` Arvind Sankar
2020-02-20 19:51 ` Arvind Sankar
2020-02-20 21:22 ` Ard Biesheuvel
2020-02-20 22:04 ` Arvind Sankar
2020-02-20 11:06 ` [RFC PATCH 2/3] efi/libstub: Introduce symbolic constants for the stub major/minor version Ard Biesheuvel
2020-02-20 11:06 ` [RFC PATCH 3/3] efi: Bump the Linux EFI stub major version number to #1 Ard Biesheuvel
2020-02-20 13:53 ` Daniel Kiper [this message]
2020-02-20 14:55 ` [RFC PATCH 0/3] efi: put an API version number in the PE/COFF header Heinrich Schuchardt
2020-02-20 19:29 ` Ard Biesheuvel
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=20200220135319.7rqromng7jmyc2rw@tomti.i.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=agraf@csgraf.de \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=leif@nuviainc.com \
--cc=lersek@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=mjg59@google.com \
--cc=nivedita@alum.mit.edu \
--cc=pjones@redhat.com \
--cc=xypron.glpk@gmx.de \
/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).