* [PATCH v2] multiboot2: clarify usage of the address tag
@ 2018-06-07 15:59 ` Roger Pau Monne
0 siblings, 0 replies; 12+ messages in thread
From: Roger Pau Monne @ 2018-06-07 15:59 UTC (permalink / raw)
To: grub-devel; +Cc: xen-devel, Daniel Kiper, Roger Pau Monne
Add a note to spell out that if the address tag is not present the
file should be loaded using the elf header.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xenproject.org
---
Changes since v1:
- s/elf/@sc{elf}/
- s/Multiboot/Multiboot2/
---
doc/multiboot.texi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..3c797787c 100644
--- a/doc/multiboot.texi
+++ b/doc/multiboot.texi
@@ -509,6 +509,12 @@ assumes that no bss segment is present.
@end table
+Note: This information does not need to be provided if the kernel image
+is in @sc{elf} format, but it must be provided if the image is in a.out
+format or in some other format. Compliant boot loaders must be able to
+load images that are either in @sc{elf} format or contain the address
+tag embedded in the Multiboot2 header.
+
@subsection The entry address tag of Multiboot2 header
@example
--
2.17.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH v2] multiboot2: clarify usage of the address tag @ 2018-06-07 15:59 ` Roger Pau Monne 0 siblings, 0 replies; 12+ messages in thread From: Roger Pau Monne @ 2018-06-07 15:59 UTC (permalink / raw) To: grub-devel; +Cc: Roger Pau Monne, Daniel Kiper, xen-devel Add a note to spell out that if the address tag is not present the file should be loaded using the elf header. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> --- Cc: Daniel Kiper <daniel.kiper@oracle.com> Cc: xen-devel@lists.xenproject.org --- Changes since v1: - s/elf/@sc{elf}/ - s/Multiboot/Multiboot2/ --- doc/multiboot.texi | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/multiboot.texi b/doc/multiboot.texi index 2e2d7e74a..3c797787c 100644 --- a/doc/multiboot.texi +++ b/doc/multiboot.texi @@ -509,6 +509,12 @@ assumes that no bss segment is present. @end table +Note: This information does not need to be provided if the kernel image +is in @sc{elf} format, but it must be provided if the image is in a.out +format or in some other format. Compliant boot loaders must be able to +load images that are either in @sc{elf} format or contain the address +tag embedded in the Multiboot2 header. + @subsection The entry address tag of Multiboot2 header @example -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-07 15:59 ` Roger Pau Monne (?) @ 2018-06-08 9:35 ` Daniel Kiper -1 siblings, 0 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-08 9:35 UTC (permalink / raw) To: Roger Pau Monne; +Cc: grub-devel, xen-devel On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > Add a note to spell out that if the address tag is not present the > file should be loaded using the elf header. > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > --- > Cc: Daniel Kiper <daniel.kiper@oracle.com> > Cc: xen-devel@lists.xenproject.org > --- > Changes since v1: > - s/elf/@sc{elf}/ > - s/Multiboot/Multiboot2/ > --- > doc/multiboot.texi | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > index 2e2d7e74a..3c797787c 100644 > --- a/doc/multiboot.texi > +++ b/doc/multiboot.texi > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > @end table > > +Note: This information does not need to be provided if the kernel image > +is in @sc{elf} format, but it must be provided if the image is in a.out > +format or in some other format. Compliant boot loaders must be able to > +load images that are either in @sc{elf} format or contain the address > +tag embedded in the Multiboot2 header. > + Now it is better. However, there is a lack of information that this tag should be preferred over the relevant data provided in the ELF header if both are available in the image. This have to be clear like it is in Multiboot spec. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-07 15:59 ` Roger Pau Monne (?) (?) @ 2018-06-08 9:35 ` Daniel Kiper 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:08 ` Roger Pau Monné -1 siblings, 2 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-08 9:35 UTC (permalink / raw) To: Roger Pau Monne; +Cc: grub-devel, xen-devel On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > Add a note to spell out that if the address tag is not present the > file should be loaded using the elf header. > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > --- > Cc: Daniel Kiper <daniel.kiper@oracle.com> > Cc: xen-devel@lists.xenproject.org > --- > Changes since v1: > - s/elf/@sc{elf}/ > - s/Multiboot/Multiboot2/ > --- > doc/multiboot.texi | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > index 2e2d7e74a..3c797787c 100644 > --- a/doc/multiboot.texi > +++ b/doc/multiboot.texi > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > @end table > > +Note: This information does not need to be provided if the kernel image > +is in @sc{elf} format, but it must be provided if the image is in a.out > +format or in some other format. Compliant boot loaders must be able to > +load images that are either in @sc{elf} format or contain the address > +tag embedded in the Multiboot2 header. > + Now it is better. However, there is a lack of information that this tag should be preferred over the relevant data provided in the ELF header if both are available in the image. This have to be clear like it is in Multiboot spec. Daniel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 9:35 ` Daniel Kiper @ 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:08 ` Roger Pau Monné 1 sibling, 0 replies; 12+ messages in thread From: Roger Pau Monné @ 2018-06-08 10:08 UTC (permalink / raw) To: Daniel Kiper; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > Add a note to spell out that if the address tag is not present the > > file should be loaded using the elf header. > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > --- > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > Cc: xen-devel@lists.xenproject.org > > --- > > Changes since v1: > > - s/elf/@sc{elf}/ > > - s/Multiboot/Multiboot2/ > > --- > > doc/multiboot.texi | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > index 2e2d7e74a..3c797787c 100644 > > --- a/doc/multiboot.texi > > +++ b/doc/multiboot.texi > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > @end table > > > > +Note: This information does not need to be provided if the kernel image > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > +format or in some other format. Compliant boot loaders must be able to > > +load images that are either in @sc{elf} format or contain the address > > +tag embedded in the Multiboot2 header. > > + > > Now it is better. However, there is a lack of information that this tag > should be preferred over the relevant data provided in the ELF header if > both are available in the image. This have to be clear like it is in > Multiboot spec. Would you be OK with adding the following sentence at the end: "When the address tag is present it must be used in order to load the image, regardless of whether an @sc{elf} header is also present." Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 9:35 ` Daniel Kiper 2018-06-08 10:08 ` Roger Pau Monné @ 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:39 ` Daniel Kiper 2018-06-08 10:39 ` Daniel Kiper 1 sibling, 2 replies; 12+ messages in thread From: Roger Pau Monné @ 2018-06-08 10:08 UTC (permalink / raw) To: Daniel Kiper; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > Add a note to spell out that if the address tag is not present the > > file should be loaded using the elf header. > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > --- > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > Cc: xen-devel@lists.xenproject.org > > --- > > Changes since v1: > > - s/elf/@sc{elf}/ > > - s/Multiboot/Multiboot2/ > > --- > > doc/multiboot.texi | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > index 2e2d7e74a..3c797787c 100644 > > --- a/doc/multiboot.texi > > +++ b/doc/multiboot.texi > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > @end table > > > > +Note: This information does not need to be provided if the kernel image > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > +format or in some other format. Compliant boot loaders must be able to > > +load images that are either in @sc{elf} format or contain the address > > +tag embedded in the Multiboot2 header. > > + > > Now it is better. However, there is a lack of information that this tag > should be preferred over the relevant data provided in the ELF header if > both are available in the image. This have to be clear like it is in > Multiboot spec. Would you be OK with adding the following sentence at the end: "When the address tag is present it must be used in order to load the image, regardless of whether an @sc{elf} header is also present." Roger. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 10:08 ` Roger Pau Monné @ 2018-06-08 10:39 ` Daniel Kiper 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 9:30 ` Roger Pau Monné 2018-06-08 10:39 ` Daniel Kiper 1 sibling, 2 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-08 10:39 UTC (permalink / raw) To: Roger Pau Monné; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 12:08:22PM +0200, Roger Pau Monné wrote: > On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > > Add a note to spell out that if the address tag is not present the > > > file should be loaded using the elf header. > > > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > > --- > > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > > Cc: xen-devel@lists.xenproject.org > > > --- > > > Changes since v1: > > > - s/elf/@sc{elf}/ > > > - s/Multiboot/Multiboot2/ > > > --- > > > doc/multiboot.texi | 6 ++++++ > > > 1 file changed, 6 insertions(+) > > > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > > index 2e2d7e74a..3c797787c 100644 > > > --- a/doc/multiboot.texi > > > +++ b/doc/multiboot.texi > > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > > > @end table > > > > > > +Note: This information does not need to be provided if the kernel image > > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > > +format or in some other format. Compliant boot loaders must be able to > > > +load images that are either in @sc{elf} format or contain the address > > > +tag embedded in the Multiboot2 header. > > > + > > > > Now it is better. However, there is a lack of information that this tag > > should be preferred over the relevant data provided in the ELF header if > > both are available in the image. This have to be clear like it is in > > Multiboot spec. > > Would you be OK with adding the following sentence at the end: > > "When the address tag is present it must be used in order to load the > image, regardless of whether an @sc{elf} header is also present." I would put this as a second sentence in note, just after "... some other format." However, then probably last sentence should be rephrased a bit. Daniel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 10:39 ` Daniel Kiper @ 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 9:30 ` Roger Pau Monné 1 sibling, 0 replies; 12+ messages in thread From: Roger Pau Monné @ 2018-06-11 9:30 UTC (permalink / raw) To: Daniel Kiper; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 12:39:28PM +0200, Daniel Kiper wrote: > On Fri, Jun 08, 2018 at 12:08:22PM +0200, Roger Pau Monné wrote: > > On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > > > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > > > Add a note to spell out that if the address tag is not present the > > > > file should be loaded using the elf header. > > > > > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > > > --- > > > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > > > Cc: xen-devel@lists.xenproject.org > > > > --- > > > > Changes since v1: > > > > - s/elf/@sc{elf}/ > > > > - s/Multiboot/Multiboot2/ > > > > --- > > > > doc/multiboot.texi | 6 ++++++ > > > > 1 file changed, 6 insertions(+) > > > > > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > > > index 2e2d7e74a..3c797787c 100644 > > > > --- a/doc/multiboot.texi > > > > +++ b/doc/multiboot.texi > > > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > > > > > @end table > > > > > > > > +Note: This information does not need to be provided if the kernel image > > > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > > > +format or in some other format. Compliant boot loaders must be able to > > > > +load images that are either in @sc{elf} format or contain the address > > > > +tag embedded in the Multiboot2 header. > > > > + > > > > > > Now it is better. However, there is a lack of information that this tag > > > should be preferred over the relevant data provided in the ELF header if > > > both are available in the image. This have to be clear like it is in > > > Multiboot spec. > > > > Would you be OK with adding the following sentence at the end: > > > > "When the address tag is present it must be used in order to load the > > image, regardless of whether an @sc{elf} header is also present." > > I would put this as a second sentence in note, just after "... some > other format." However, then probably last sentence should be rephrased > a bit. I think the following is clear enough: "Note: This information does not need to be provided if the kernel image is in @sc{elf} format, but it must be provided if the image is in a.out format or in some other format. When the address tag is present it must be used in order to load the image, regardless of whether an @sc{elf} header is also present. Compliant boot loaders must be able to load images that are either in @sc{elf} format or contain the address tag embedded in the Multiboot2 header." Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 10:39 ` Daniel Kiper 2018-06-11 9:30 ` Roger Pau Monné @ 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 11:16 ` Daniel Kiper 2018-06-11 11:16 ` Daniel Kiper 1 sibling, 2 replies; 12+ messages in thread From: Roger Pau Monné @ 2018-06-11 9:30 UTC (permalink / raw) To: Daniel Kiper; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 12:39:28PM +0200, Daniel Kiper wrote: > On Fri, Jun 08, 2018 at 12:08:22PM +0200, Roger Pau Monné wrote: > > On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > > > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > > > Add a note to spell out that if the address tag is not present the > > > > file should be loaded using the elf header. > > > > > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > > > --- > > > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > > > Cc: xen-devel@lists.xenproject.org > > > > --- > > > > Changes since v1: > > > > - s/elf/@sc{elf}/ > > > > - s/Multiboot/Multiboot2/ > > > > --- > > > > doc/multiboot.texi | 6 ++++++ > > > > 1 file changed, 6 insertions(+) > > > > > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > > > index 2e2d7e74a..3c797787c 100644 > > > > --- a/doc/multiboot.texi > > > > +++ b/doc/multiboot.texi > > > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > > > > > @end table > > > > > > > > +Note: This information does not need to be provided if the kernel image > > > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > > > +format or in some other format. Compliant boot loaders must be able to > > > > +load images that are either in @sc{elf} format or contain the address > > > > +tag embedded in the Multiboot2 header. > > > > + > > > > > > Now it is better. However, there is a lack of information that this tag > > > should be preferred over the relevant data provided in the ELF header if > > > both are available in the image. This have to be clear like it is in > > > Multiboot spec. > > > > Would you be OK with adding the following sentence at the end: > > > > "When the address tag is present it must be used in order to load the > > image, regardless of whether an @sc{elf} header is also present." > > I would put this as a second sentence in note, just after "... some > other format." However, then probably last sentence should be rephrased > a bit. I think the following is clear enough: "Note: This information does not need to be provided if the kernel image is in @sc{elf} format, but it must be provided if the image is in a.out format or in some other format. When the address tag is present it must be used in order to load the image, regardless of whether an @sc{elf} header is also present. Compliant boot loaders must be able to load images that are either in @sc{elf} format or contain the address tag embedded in the Multiboot2 header." Roger. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-11 9:30 ` Roger Pau Monné @ 2018-06-11 11:16 ` Daniel Kiper 2018-06-11 11:16 ` Daniel Kiper 1 sibling, 0 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-11 11:16 UTC (permalink / raw) To: Roger Pau Monné; +Cc: grub-devel, xen-devel On Mon, Jun 11, 2018 at 11:30:16AM +0200, Roger Pau Monné wrote: [...] > I think the following is clear enough: > > "Note: This information does not need to be provided if the kernel image is in > @sc{elf} format, but it must be provided if the image is in a.out format or in > some other format. When the address tag is present it must be used in order to > load the image, regardless of whether an @sc{elf} header is also present. > Compliant boot loaders must be able to load images that are either in @sc{elf} > format or contain the address tag embedded in the Multiboot2 header." LGTM. Thanks! Daniel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 11:16 ` Daniel Kiper @ 2018-06-11 11:16 ` Daniel Kiper 1 sibling, 0 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-11 11:16 UTC (permalink / raw) To: Roger Pau Monné; +Cc: grub-devel, xen-devel On Mon, Jun 11, 2018 at 11:30:16AM +0200, Roger Pau Monné wrote: [...] > I think the following is clear enough: > > "Note: This information does not need to be provided if the kernel image is in > @sc{elf} format, but it must be provided if the image is in a.out format or in > some other format. When the address tag is present it must be used in order to > load the image, regardless of whether an @sc{elf} header is also present. > Compliant boot loaders must be able to load images that are either in @sc{elf} > format or contain the address tag embedded in the Multiboot2 header." LGTM. Thanks! Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH v2] multiboot2: clarify usage of the address tag 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:39 ` Daniel Kiper @ 2018-06-08 10:39 ` Daniel Kiper 1 sibling, 0 replies; 12+ messages in thread From: Daniel Kiper @ 2018-06-08 10:39 UTC (permalink / raw) To: Roger Pau Monné; +Cc: grub-devel, xen-devel On Fri, Jun 08, 2018 at 12:08:22PM +0200, Roger Pau Monné wrote: > On Fri, Jun 08, 2018 at 11:35:52AM +0200, Daniel Kiper wrote: > > On Thu, Jun 07, 2018 at 05:59:06PM +0200, Roger Pau Monne wrote: > > > Add a note to spell out that if the address tag is not present the > > > file should be loaded using the elf header. > > > > > > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > > > --- > > > Cc: Daniel Kiper <daniel.kiper@oracle.com> > > > Cc: xen-devel@lists.xenproject.org > > > --- > > > Changes since v1: > > > - s/elf/@sc{elf}/ > > > - s/Multiboot/Multiboot2/ > > > --- > > > doc/multiboot.texi | 6 ++++++ > > > 1 file changed, 6 insertions(+) > > > > > > diff --git a/doc/multiboot.texi b/doc/multiboot.texi > > > index 2e2d7e74a..3c797787c 100644 > > > --- a/doc/multiboot.texi > > > +++ b/doc/multiboot.texi > > > @@ -509,6 +509,12 @@ assumes that no bss segment is present. > > > > > > @end table > > > > > > +Note: This information does not need to be provided if the kernel image > > > +is in @sc{elf} format, but it must be provided if the image is in a.out > > > +format or in some other format. Compliant boot loaders must be able to > > > +load images that are either in @sc{elf} format or contain the address > > > +tag embedded in the Multiboot2 header. > > > + > > > > Now it is better. However, there is a lack of information that this tag > > should be preferred over the relevant data provided in the ELF header if > > both are available in the image. This have to be clear like it is in > > Multiboot spec. > > Would you be OK with adding the following sentence at the end: > > "When the address tag is present it must be used in order to load the > image, regardless of whether an @sc{elf} header is also present." I would put this as a second sentence in note, just after "... some other format." However, then probably last sentence should be rephrased a bit. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2018-06-11 11:16 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-06-07 15:59 [PATCH v2] multiboot2: clarify usage of the address tag Roger Pau Monne 2018-06-07 15:59 ` Roger Pau Monne 2018-06-08 9:35 ` Daniel Kiper 2018-06-08 9:35 ` Daniel Kiper 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:08 ` Roger Pau Monné 2018-06-08 10:39 ` Daniel Kiper 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 9:30 ` Roger Pau Monné 2018-06-11 11:16 ` Daniel Kiper 2018-06-11 11:16 ` Daniel Kiper 2018-06-08 10:39 ` Daniel Kiper
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.