From: Daniel Kiper <daniel.kiper@oracle.com>
To: grub-devel@gnu.org, xen-devel@lists.xenproject.org
Cc: andrew.cooper3@citrix.com, arvidjaar@gmail.com,
eric.snowberg@oracle.com, jgross@suse.com,
konrad.wilk@oracle.com, phcoder@gmail.com,
seth.goldberg@oracle.com
Subject: [MULTIBOOT2 DOC PATCH 00/10] multiboot2: Update documentation
Date: Thu, 9 Jun 2016 22:30:34 +0200 [thread overview]
Message-ID: <1465504244-17175-1-git-send-email-daniel.kiper@oracle.com> (raw)
Hi,
This patch series adds descriptions of multiboot2 protocol new
features and fixes some issues found here and there.
It applies to multiboot2 branch in GRUB2 git tree.
Daniel
PS Please apply my GRUB2 patches which add above mentioned
features. They were posted at the of March.
configure.ac | 2 +-
doc/multiboot.texi | 255 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
doc/multiboot2.h | 42 ++++++++++++++++
3 files changed, 282 insertions(+), 17 deletions(-)
Daniel Kiper (10):
multiboot2: Remove redundant if
multiboot2: Clarify meaning of information request header tag
multiboot2: Fix description of EFI boot services tag
multiboot2: Add description of support for EFI boot services
multiboot2: Add description of EFI image handle tags
multiboot2: Add description of support for relocatable images
multiboot2: Say that memory maps may not be available on EFI platforms
multiboot2: Add C structure alignment and padding consideration section
multiboot2: Add me to authors
multiboot2: Bump version to 2.0
next reply other threads:[~2016-06-09 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:30 Daniel Kiper [this message]
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 01/10] multiboot2: Remove redundant if Daniel Kiper
2016-06-09 21:02 ` Andrew Cooper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 02/10] multiboot2: Clarify meaning of information request header tag Daniel Kiper
2016-06-09 21:14 ` [Xen-devel] " Andrew Cooper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 03/10] multiboot2: Fix description of EFI boot services tag Daniel Kiper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 04/10] multiboot2: Add description of support for EFI boot services Daniel Kiper
2016-06-09 21:31 ` Andrew Cooper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 05/10] multiboot2: Add description of EFI image handle tags Daniel Kiper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 06/10] multiboot2: Add description of support for relocatable images Daniel Kiper
2016-06-09 21:36 ` [Xen-devel] " Andrew Cooper
2016-06-10 17:36 ` Daniel Kiper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 07/10] multiboot2: Say that memory maps may not be available on EFI platforms Daniel Kiper
2016-06-09 21:37 ` Andrew Cooper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 08/10] multiboot2: Add C structure alignment and padding consideration section Daniel Kiper
2016-06-09 22:07 ` Andrew Cooper
2016-06-10 17:58 ` Daniel Kiper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 09/10] multiboot2: Add me to authors Daniel Kiper
2016-06-09 20:30 ` [MULTIBOOT2 DOC PATCH 10/10] multiboot2: Bump version to 2.0 Daniel Kiper
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=1465504244-17175-1-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=arvidjaar@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=phcoder@gmail.com \
--cc=seth.goldberg@oracle.com \
--cc=xen-devel@lists.xenproject.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).