From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] ARM: l2x0: Add OF based initialization
Date: Fri, 08 Jul 2011 12:59:47 -0500 [thread overview]
Message-ID: <4E174593.20107@gmail.com> (raw)
In-Reply-To: <201107062326.53737.arnd@arndb.de>
Russell,
On 07/06/2011 04:26 PM, Arnd Bergmann wrote:
> On Wednesday 06 July 2011 23:02:37 Grant Likely wrote:
>>
>> On Wed, Jul 06, 2011 at 03:42:59PM -0500, Rob Herring wrote:
>>> From: Rob Herring <rob.herring@calxeda.com>
>>>
>>> This adds probing for ARM L2x0 cache controllers via device tree. Support
>>> includes the L210, L220, and PL310 controllers. The binding allows setting
>>> up cache RAM latencies and filter addresses (PL310 only).
>>>
>>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>>
>> Acked-by: Grant Likely <grant.likely@secretlab.ca>
>>
>> By rights, this should go via the arm tree, but it depends on patches
>> that are already in devicetree/next. Arnd, how do you want to handle
>> this? I want to avoid rebasing devicetree/next.
>
> It's outside of the scope of the arm-soc tree really, the l2x0 code
> is clearly core arm stuff, so it belongs into Russell's tree.
>
> I think it's best if Russell can provide an Ack for this and you
> put it in the tree that already has the dependencies.
>
Any comments?
Rob
next prev parent reply other threads:[~2011-07-08 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 20:42 [PATCH 1/2] dt: add helper function to read u32 arrays Rob Herring
2011-07-06 20:42 ` [PATCH v4 2/2] ARM: l2x0: Add OF based initialization Rob Herring
2011-07-06 20:52 ` Arnd Bergmann
2011-07-06 21:02 ` Grant Likely
2011-07-06 21:26 ` Arnd Bergmann
2011-07-08 17:59 ` Rob Herring [this message]
2011-07-18 2:01 ` Rob Herring
2011-08-03 18:41 ` Rob Herring
2011-07-07 0:20 ` Olof Johansson
2011-07-28 6:17 ` Barry Song
2011-07-06 20:59 ` [PATCH 1/2] dt: add helper function to read u32 arrays Grant Likely
2011-07-08 1:45 ` Shawn Guo
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=4E174593.20107@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).