From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 09/10] xen: arm: update multiboot device tree bindings.
Date: Mon, 21 Jul 2014 12:53:00 +0100 [thread overview]
Message-ID: <53CCFF1C.10607@linaro.org> (raw)
In-Reply-To: <1405943128.25022.37.camel@kazak.uk.xensource.com>
On 07/21/2014 12:45 PM, Ian Campbell wrote:
> On Fri, 2014-07-18 at 22:03 +0100, Julien Grall wrote:
>> Hi Ian,
>>
>> On 18/07/14 14:08, Ian Campbell wrote:
>>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>
>> Acked-by: Julien Grall <julien.grall@linaro.org>
>
> Thanks. I've applied patches 1..9 of this series. I'll resend 10 ASAP
> with the change you've suggested.
>
> On my potential backports list I've got:
> xen: arm: implement generic multiboot compatibility strings
> xen: arm: /chosen/module@N/bootargs bootprotcol node is not deprecated
>
> I don't think anything else here is suitable for backport. Let me know
> if you think something is (or isn't)
I would also update the document bindings in
docs/misc/arm/device-tree/booting.txt.
The patch #9 looks the good one for this purpose. Minus the unspecified
type example.
BTW, I don't find anything in the documentation talking about bootmodule
type detection by ordering. Is this intended?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-07-21 11:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 13:07 [PATCH v3 00/10] xen: arm: Refactor/improve early DT parsing and multiboot module support Ian Campbell
2014-07-18 13:08 ` [PATCH v3 01/10] xen: arm: implement generic multiboot compatibility strings Ian Campbell
2014-07-18 13:08 ` [PATCH v3 02/10] xen: arm: /chosen/module@N/bootargs bootprotcol node is not deprecated Ian Campbell
2014-07-18 13:08 ` [PATCH v3 03/10] xen: arm: prefer typesafe max()/min() over MAX()/MIN() Ian Campbell
2014-07-18 13:08 ` [PATCH v3 04/10] xen: arm: rename early_info structs Ian Campbell
2014-07-18 13:08 ` [PATCH v3 05/10] xen: arm: move boot time fdt parsing into separate file Ian Campbell
2014-07-18 13:08 ` [PATCH v3 06/10] xen: arm: move device_tree_bootargs to bootfdt.c, renaming to boot_fdt_cmdline Ian Campbell
2014-07-18 13:08 ` [PATCH v3 07/10] xen: arm: store per-boot module type instead of relying on index Ian Campbell
2014-07-18 20:52 ` Julien Grall
2014-07-18 13:08 ` [PATCH v3 08/10] xen: arm: support bootmodule type detection by ordering Ian Campbell
2014-07-18 21:02 ` Julien Grall
2014-07-21 10:18 ` Ian Campbell
2014-07-18 13:08 ` [PATCH v3 09/10] xen: arm: update multiboot device tree bindings Ian Campbell
2014-07-18 21:03 ` Julien Grall
2014-07-21 11:45 ` Ian Campbell
2014-07-21 11:53 ` Julien Grall [this message]
2014-07-21 12:18 ` Ian Campbell
2014-07-21 12:23 ` Julien Grall
2014-07-21 12:26 ` Ian Campbell
2014-07-21 12:34 ` Julien Grall
2014-07-24 14:30 ` Ian Campbell
2014-07-24 14:33 ` Julien Grall
2014-07-24 15:12 ` Ian Campbell
2014-07-18 13:08 ` [PATCH v3 10/10] xen: arm: Only lookup kernel bootmodule once while building dom0 dtb Ian Campbell
2014-07-18 21:06 ` Julien Grall
2014-07-21 10:20 ` Ian Campbell
2014-07-21 11:48 ` [PATCH v3 00/10] xen: arm: Refactor/improve early DT parsing and multiboot module support Ian Campbell
2014-07-22 3:20 ` 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=53CCFF1C.10607@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--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 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).