From: Julien Grall <julien.grall@arm.com>
To: fu.wei@linaro.org, grub-devel@gnu.org, arvidjaar@gmail.com,
phcoder@gmail.com
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com,
jcm@redhat.com, leif.lindholm@linaro.org, sstabellini@kernel.org,
linaro-uefi@lists.linaro.org
Subject: Re: [PATCH v5 4/4] arm64: update the introduction of xen boot commands in docs/grub.texi
Date: Tue, 12 Jul 2016 11:13:56 +0100 [thread overview]
Message-ID: <5784C2E4.1030607@arm.com> (raw)
In-Reply-To: <1467827637-14508-5-git-send-email-fu.wei@linaro.org>
Hi Fu Wei,
On 06/07/16 18:53, fu.wei@linaro.org wrote:
> From: Fu Wei <fu.wei@linaro.org>
>
> delete: xen_linux, xen_initrd, xen_xsm
> add: xen_module
>
> This update bases on
> commit 0edd750e50698854068358ea53528100a9192902
> Author: Vladimir Serbinenko <phcoder@gmail.com>
> Date: Fri Jan 22 10:18:47 2016 +0100
>
> xen_boot: Remove obsolete module type distinctions.
>
> Also bases on the module loading mechanism of Xen code:
> 488c2a8 docs/arm64: clarify the documention for loading XSM support
> 67831c4 docs/arm64: update the documentation for loading XSM support
> ca32012 xen/arm64: check XSM Magic from the second unknown module.
>
> Signed-off-by: Fu Wei <fu.wei@linaro.org>
Reviewed-by: Julien Grall <julien.grall@arm.com>
Regards,
--
Julien Grall
prev parent reply other threads:[~2016-07-12 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 17:53 [PATCH v5 0/4] arm64,xen: add xen_boot support into grup-mkconfig fu.wei
2016-07-06 17:53 ` [PATCH v5 1/4] i386, xen: Add xen_hypervisor and xen_module aliases for i386 fu.wei
2016-07-06 17:53 ` [PATCH v5 2/4] arm64: add "--nounzip" option support in xen_module command fu.wei
2016-07-06 17:53 ` [PATCH v5 3/4] * util/grub.d/20_linux_xen.in: Add xen_boot command support fu.wei
2016-07-12 10:21 ` Julien Grall
2016-07-26 8:13 ` Fu Wei
2016-07-06 17:53 ` [PATCH v5 4/4] arm64: update the introduction of xen boot commands in docs/grub.texi fu.wei
2016-07-12 10:13 ` Julien Grall [this message]
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=5784C2E4.1030607@arm.com \
--to=julien.grall@arm.com \
--cc=Ian.Campbell@citrix.com \
--cc=arvidjaar@gmail.com \
--cc=fu.wei@linaro.org \
--cc=grub-devel@gnu.org \
--cc=jcm@redhat.com \
--cc=leif.lindholm@linaro.org \
--cc=linaro-uefi@lists.linaro.org \
--cc=phcoder@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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).