From: Jamie Iles <jamie@jamieiles.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
marc.zyngier@arm.com, thomas.abraham@linaro.org,
jamie@jamieiles.com, b-cousson@ti.com, shawn.guo@linaro.org,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 0/2] GIC OF bindings
Date: Thu, 29 Sep 2011 10:21:49 +0100 [thread overview]
Message-ID: <20110929092149.GL17204@pulham.picochip.com> (raw)
In-Reply-To: <1317268436-1613-1-git-send-email-robherring2@gmail.com>
On Wed, Sep 28, 2011 at 10:53:54PM -0500, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> With recent patches for VIC device tree support and GIC MULTI_IRQ support,
> it is evident that the irq domain support should be moved into the core GIC
> code and not be dependent on the DT initialization. So I've split things up
> into 2 patches separating irq_domain and device-tree code.
>
> This should only change the internals of the GIC code. The binding is
> unchanged from the previous version. Yeah!
>
> The full series is available here. This includes Russell's devel-stable and
> for-next branches and Nico's vmalloc branch.
Looks good to me!
Reviewed-by: Jamie Iles <jamie@jamieiles.com>
prev parent reply other threads:[~2011-09-29 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 3:53 [PATCH 0/2] GIC OF bindings Rob Herring
[not found] ` <1317268436-1613-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-29 3:53 ` [PATCH 1/2] ARM: gic: add irq_domain support Rob Herring
[not found] ` <1317268436-1613-2-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-29 17:15 ` Grant Likely
2011-09-29 21:02 ` Rob Herring
2011-09-30 0:27 ` Grant Likely
2011-09-29 3:53 ` [PATCH 2/2] ARM: gic: add OF based initialization Rob Herring
2011-09-29 17:19 ` Grant Likely
2011-09-29 9:21 ` Jamie Iles [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=20110929092149.GL17204@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=thomas.abraham@linaro.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).