grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: daniel.kiper@oracle.com, xen-devel@lists.xenproject.org,
	grub-devel@gnu.org
Subject: [PATCH] Fix ARM multiboot2 breaking Fedora.
Date: Mon, 28 Aug 2017 14:40:13 -0400	[thread overview]
Message-ID: <1503945615-1720-1-git-send-email-konrad.wilk@oracle.com> (raw)

Hey,

The first patch:
 [PATCH 1/2] Fix util/grub.d/20_linux_xen.in: Add xen_boot command

is a fix discovered on Fedora rawhide where I was surprised to see that
grub2-mkconfig would not create a configuration file anymore.
See https://bugzilla.redhat.com/show_bug.cgi?id=1486002 for details.


The second patch has been posted in the past
(https://lists.xen.org/archives/html/xen-devel/2017-03/txtCeHTNmz1hZ.txt)

 [PATCH 2/2] Use grub-file to figure out whether multiboot2 should be

and just allows us to multiboot2 instead of multiboot if the binary
supports it.


 util/grub.d/20_linux_xen.in | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

Konrad Rzeszutek Wilk (2):
      Fix util/grub.d/20_linux_xen.in: Add xen_boot command support for aarch64
      Use grub-file to figure out whether multiboot2 should be used for Xen.gz



             reply	other threads:[~2017-08-28 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 18:40 Konrad Rzeszutek Wilk [this message]
2017-08-28 18:40 ` [PATCH 1/2] Fix util/grub.d/20_linux_xen.in: Add xen_boot command support for aarch64 Konrad Rzeszutek Wilk
2017-08-28 18:42   ` Konrad Rzeszutek Wilk
2017-08-29 18:58     ` Daniel Kiper
2017-08-29  7:12   ` Fu Wei Fu
2017-08-29 13:29     ` Konrad Rzeszutek Wilk
2017-08-28 18:40 ` [PATCH 2/2] Use grub-file to figure out whether multiboot2 should be used for Xen.gz Konrad Rzeszutek Wilk
2017-08-29 19:04   ` 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=1503945615-1720-1-git-send-email-konrad.wilk@oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=daniel.kiper@oracle.com \
    --cc=grub-devel@gnu.org \
    --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).