From: Matt Fleming <matt@codeblueprint.co.uk>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
x86@kernel.org, corbet@lwn.net, hpa@zytor.com, bp@alien8.de,
mingo@redhat.com, tglx@linutronix.de, konrad.wilk@oracle.com,
mfleming@suse.com, ross.philipson@oracle.com,
daniel.kiper@oracle.com
Subject: Re: [PATCH] doc: add boot protocol 2.13 description to Documentation/x86/boot.txt
Date: Mon, 18 Mar 2019 09:44:12 +0000 [thread overview]
Message-ID: <20190318094412.GA18161@codeblueprint.co.uk> (raw)
In-Reply-To: <20190308114310.25041-1-jgross@suse.com>
On Fri, 08 Mar, at 12:43:10PM, Juergen Gross wrote:
> Documentation/x86/boot.txt is missing protocol 2.13 description.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> Documentation/x86/boot.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
> index f4c2a97bfdbd..223e484a1304 100644
> --- a/Documentation/x86/boot.txt
> +++ b/Documentation/x86/boot.txt
> @@ -61,6 +61,10 @@ Protocol 2.12: (Kernel 3.8) Added the xloadflags field and extension fields
> to struct boot_params for loading bzImage and ramdisk
> above 4G in 64bit.
>
> +Protocol 2.13: (Kernel 3.14) Support 32- and 64-bit flags being set in
> + xloadflags to support booting a 64-bit kernel from 32-bit
> + EFI
> +
> **** MEMORY LAYOUT
>
> The traditional memory map for the kernel loader, used for Image or
> --
> 2.16.4
Not sure if this has already been picked up but...
Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>
next prev parent reply other threads:[~2019-03-18 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 11:43 [PATCH] doc: add boot protocol 2.13 description to Documentation/x86/boot.txt Juergen Gross
2019-03-08 12:05 ` Daniel Kiper
2019-03-08 13:12 ` Konrad Rzeszutek Wilk
2019-03-11 23:34 ` hpa
2019-03-18 9:44 ` Matt Fleming [this message]
2019-03-18 17:50 ` Jonathan Corbet
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=20190318094412.GA18161@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.kiper@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfleming@suse.com \
--cc=mingo@redhat.com \
--cc=ross.philipson@oracle.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;
as well as URLs for NNTP newsgroup(s).