linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFT 1/2] drivers: bus: check cci device tree node status
Date: Fri, 09 Jan 2015 10:40:42 +0530	[thread overview]
Message-ID: <54AF62D2.7000400@arm.com> (raw)
In-Reply-To: <CAM4voamaqoje8Ccz3+UxvxaHN6GBd=QC5wRjVcz9Osfc=4aeiw@mail.gmail.com>



On Thursday 08 January 2015 08:57 PM, Abhilash Kesavan wrote:
> Hi Sudeep,
>
> On Thu, Jan 8, 2015 at 12:15 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> Hi Abhilash,

[...]

>>
>> What's the status of this patch. It was useful for me on vexpress for some
>> testing. Please feel free to add
>>
>> Tested-by: Sudeep Holla <sudeep.holla@arm.com>
>>
>> if this is not yet queued.
>
> Thanks for the tested-by. This patch has not been merged yet; I am not
> quite sure who is supposed to pick this up.
>

So far, most of the CCI patches are merged through arm-soc.

Regards,
Sudeep

  reply	other threads:[~2015-01-09  5:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 14:50 [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-11-28 14:50 ` [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa Abhilash Kesavan
2014-11-28 15:19   ` Krzysztof Kozlowski
2014-11-28 15:39     ` Abhilash Kesavan
2014-12-01  9:03       ` Krzysztof Kozlowski
2014-12-01 11:09         ` Russell King - ARM Linux
2014-12-01 11:19           ` Krzysztof Kozlowski
2014-12-01 18:50   ` Kevin Hilman
2014-12-01 19:52     ` Tyler Baker
2014-12-10  4:01 ` [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-12-10  4:14   ` Sudeep Holla
2014-12-10  4:25     ` Abhilash Kesavan
2014-12-10  5:16       ` Sudeep Holla
2015-01-08  6:45         ` Sudeep Holla
2015-01-08 15:27           ` Abhilash Kesavan
2015-01-09  5:10             ` Sudeep Holla [this message]
2015-01-09 16:28               ` Abhilash Kesavan
2015-01-09 21:09                 ` Kevin Hilman
2015-01-10  3:21                   ` Abhilash Kesavan
2014-12-10 18:29   ` Nicolas Pitre

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=54AF62D2.7000400@arm.com \
    --to=sudeep.holla@arm.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).