From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir (Xen.org)" <keir@xen.org>
Subject: Re: [PATCH 7/8] arm, device tree: parse the DTB for RAM location and size
Date: Mon, 13 Feb 2012 15:46:27 +0000 [thread overview]
Message-ID: <4F393053.80903@citrix.com> (raw)
In-Reply-To: <1329144704.31256.114.camel@zakaz.uk.xensource.com>
On 13/02/12 14:51, Ian Campbell wrote:
> On Mon, 2012-02-13 at 13:18 +0000, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> Prior to setting up the page tables, parse the DTB for the location
>> and size of RAM.
>>
>> Use this information to get the physical address to relocate Xen to in
>> setup_pagetables().
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>> Acked-by: Tim Deegan <tim@xen.org>
>> ---
> [...]
>> xen/common/Makefile | 3 +
>> xen/common/device_tree.c | 179 +++++++++++++++++++++++++++++++++++++++++
> [...]
>> xen/include/xen/device_tree.h | 36 ++++++++
>
> I'd have preferred these non-ARM bits in a separate patch if possible.
> I'm going to commit them anyway though on the basis that they are in
> reality ARM specific unless Keir (or someone else) objects quite soon.
Dividing maintainer-ship by directory seems a little coarse grained. It
may be more practical for you (Ian) to be the maintainer/committer for
the device tree related stuff even though they live under xen/common/.
Or, if you prefer, I can make sure to split the patches in common and
arch bits.
David
next prev parent reply other threads:[~2012-02-13 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:18 [PATCH 0/8] arm: initial device tree support (#3) David Vrabel
2012-02-13 13:18 ` [PATCH 1/8] libfdt: add version 1.3.0 David Vrabel
2012-02-13 13:18 ` [PATCH 2/8] libfdt: fixup libfdt_env.h for xen David Vrabel
2012-02-13 13:18 ` [PATCH 3/8] libfdt: add to build David Vrabel
2012-02-13 13:18 ` [PATCH 4/8] arm: link a device tree blob into the xen image David Vrabel
2012-02-17 17:13 ` Ian Campbell
2012-02-17 17:22 ` David Vrabel
2012-02-20 17:20 ` Ian Campbell
2012-02-22 14:34 ` Ian Campbell
2012-02-13 13:18 ` [PATCH 5/8] arm: map device tree blob in initial page tables David Vrabel
2012-02-13 13:18 ` [PATCH 6/8] arm: add early_printk() David Vrabel
2012-02-13 13:18 ` [PATCH 7/8] arm, device tree: parse the DTB for RAM location and size David Vrabel
2012-02-13 14:51 ` Ian Campbell
2012-02-13 15:46 ` David Vrabel [this message]
2012-02-13 16:53 ` Ian Campbell
2012-02-13 17:41 ` Ian Jackson
2012-03-14 10:53 ` Ian Campbell
2012-02-13 13:18 ` [PATCH 8/8] arm: setup MM using information from the device tree David Vrabel
2012-02-13 15:27 ` [PATCH 0/8] arm: initial device tree support (#3) Ian Campbell
2012-02-13 15:49 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 13:03 [PATCH 0/8] arm: initial device tree support (#2) David Vrabel
2012-02-10 13:03 ` [PATCH 7/8] arm, device tree: parse the DTB for RAM location and size David Vrabel
2012-02-10 13:25 ` Tim Deegan
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=4F393053.80903@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=keir@xen.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 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.