All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	The development of GRUB 2 <grub-devel@gnu.org>,
	Fu Wei <fu.wei@linaro.org>,
	 "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH GRUB] Allow initrd concatenation on ARM64
Date: Thu, 12 Nov 2015 14:48:54 +0100	[thread overview]
Message-ID: <564498C6.40002@gmail.com> (raw)
In-Reply-To: <1447334827.18450.73.camel@citrix.com>

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

On 12.11.2015 14:27, Ian Campbell wrote:
> On Thu, 2015-11-12 at 14:08 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
> wrote:
>> While on it also change "xen_linux" to "xen_kernel" to be vendor-neutral
>> Could someone test please? I only compile-tested it
> 
> I was expecting this patch to include a change
> to ./util/grub.d/20_linux_xen.in to update the naming there, but it looks
> like that aspect of the original series isn't in tree yet?
> 
We need to figure out what we should do on x86 wrt multiboot vs
multiboot2 before adapting 20_linux_xen
> BTW, you have a stray "linux" in the description of the (now) xen_kernel
> command.
> 
Fixed locally, thank you
> Ian.
> 
> .
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2015-11-12 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 13:08 [PATCH GRUB] Allow initrd concatenation on ARM64 Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-12 13:27 ` Ian Campbell
2015-11-12 13:27 ` [Xen-devel] " Ian Campbell
2015-11-12 13:48   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2016-02-22 15:40     ` Fu Wei
2016-02-22 15:40     ` Fu Wei
2015-11-12 13:48   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-12 13:30 ` Fu Wei
2015-11-12 13:30 ` Fu Wei

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=564498C6.40002@gmail.com \
    --to=phcoder@gmail.com \
    --cc=fu.wei@linaro.org \
    --cc=grub-devel@gnu.org \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 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.