From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Cc: "grant.likely@linaro.org" <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>
Subject: Re: [PATCH 2/2] of: move definition of of_find_next_cache_node into common code.
Date: Fri, 01 Nov 2013 19:16:21 +1100 [thread overview]
Message-ID: <1383293781.28909.39.camel@pasglop> (raw)
In-Reply-To: <527231DA.9060002@arm.com>
On Thu, 2013-10-31 at 10:32 +0000, Sudeep KarkadaNagesha wrote:
> Thanks for the follow up. Grant wanted to see usage of this outside PPC and I
> pointed him[0] to the RFC[1] I had posted to support cacheinfo on ARM.
>
> These patches are based on v3.12-rc1, let me know if you want me to
> rebase/repost on any particular version.
I've applied them to powerpc-next
Cheers,
Ben.
next prev parent reply other threads:[~2013-11-01 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 10:53 [PATCH 0/2] move of_find_next_cache_node to DT core Sudeep KarkadaNagesha
2013-09-18 10:53 ` [PATCH 1/2] powerpc: remove big endianness assumption in of_find_next_cache_node Sudeep KarkadaNagesha
2013-09-18 10:53 ` [PATCH 2/2] of: move definition of of_find_next_cache_node into common code Sudeep KarkadaNagesha
2013-10-31 5:20 ` Benjamin Herrenschmidt
2013-10-31 10:32 ` Sudeep KarkadaNagesha
2013-11-01 8:16 ` Benjamin Herrenschmidt [this message]
2013-09-18 14:51 ` [PATCH 0/2] move of_find_next_cache_node to DT core Grant Likely
2013-09-18 16:18 ` Sudeep KarkadaNagesha
2013-10-04 10:42 ` Sudeep KarkadaNagesha
2013-11-02 18:06 ` Grant Likely
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=1383293781.28909.39.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Sudeep.KarkadaNagesha@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rob.herring@calxeda.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).