From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel Kiper <daniel.kiper@oracle.com>,
grub-devel@gnu.org, xen-devel@lists.xenproject.org
Cc: jgross@suse.com, eric.snowberg@oracle.com, arvidjaar@gmail.com,
seth.goldberg@oracle.com, phcoder@gmail.com
Subject: Re: [Xen-devel] [MULTIBOOT2 DOC PATCH 02/10] multiboot2: Clarify meaning of information request header tag
Date: Thu, 9 Jun 2016 22:14:02 +0100 [thread overview]
Message-ID: <cbd38c61-6b49-a01e-a1c9-afc7a6a5326c@citrix.com> (raw)
In-Reply-To: <1465504244-17175-3-git-send-email-daniel.kiper@oracle.com>
On 09/06/2016 21:30, Daniel Kiper wrote:
> Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
> ---
> doc/multiboot.texi | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> index 27e5a2f..a7e3584 100644
> --- a/doc/multiboot.texi
> +++ b/doc/multiboot.texi
> @@ -443,15 +443,19 @@ u32[n] | mbi_tag_types |
> @end group
> @end example
>
> -@samp{mbi_tag_types} is an array of u32 each one representing an information
> -request
> -If this tag is present and @samp{optional} is set to @samp{0} information
> -conveyed by requested tag types must be present. If bootloader is unable
> -to supply this information it must fail with an error
> +@samp{mbi_tag_types} is an array of u32 each one representing an information request.
"u32's, each"
>
> -Note: it doesn't garantee that any tags of type @samp{mbi_tag_types} will
> -actually be present. E.g. on a videoless system even if you requested tag
> -@samp{8} no tags of type @samp{8} will be present in mbi.
> +If this tag is present and @samp{optional} is set to @samp{0} bootloader must
", the bootloader"
> +support (understand meaning of) requested tag(s) and be able to provide relevant
"the requested". I don't think you need to explain what supported
means, so I would just drop the brackets entirely.
> +information to image if it is available. If bootloader do not understand meaning
"the image". "the bootloader does not". "the meaning".
> +of requested tag(s) it must fail with an error. However, if it support a given
"the requested". "supports".
> +tag(s) but information conveyed by it/them is not available bootloader can do not
"a given tag(s)" is an odd way of phrasing this. I would recommend just
"supports a given tag, but the information requested by it is".
"available, the bootloader can't provide the requested".
> +provide requested tag(s) in Multiboot information structure and proceed further.
"in the Multiboot". What do you mean by "and proceed further" in this
case? It also doesn't parse. I presume you mean that it is legal for
the bootloader to not provide the requested information, but may
continue booting.
> +
> +Note: Above means that there is not guarantee that any tags of type @samp{mbi_tag_types}
"The above", "there is no guarentee"
> +will actually be present. E.g. on a videoless system even if you requested tag @samp{8}
> +and bootloader support it no tags of type @samp{8} will be present in Multiboot
"the bootloader supports it, no". "The Multiboot".
~Andrew
> +information structure.
>
>
> @node Address header tag
next prev parent reply other threads:[~2016-06-09 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:30 [MULTIBOOT2 DOC PATCH 00/10] multiboot2: Update documentation Daniel Kiper
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 ` Andrew Cooper [this message]
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=cbd38c61-6b49-a01e-a1c9-afc7a6a5326c@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=arvidjaar@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.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).