From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: Mike Leach <mike.leach@arm.com>,
Michael Williams <Michael.Williams@arm.com>,
Al Grant <al.grant@arm.com>, "Jeremiassen\, Tor" <tor@ti.com>,
Nicolas GUION <nicolas.guion@st.com>,
Pratik Patel <pratikp@codeaurora.org>,
Lyra Zhang <zhang.lyra@gmail.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-api@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH V5 0/4] Introduce CoreSight STM support
Date: Wed, 20 Apr 2016 20:08:49 +0300 [thread overview]
Message-ID: <87fuug9pi6.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CANLsYkwtHeXRwM98J3GQDpKwPcqAKXUFW6OWE5TJ6P_Og4RLZA@mail.gmail.com>
Mathieu Poirier <mathieu.poirier@linaro.org> writes:
> On 6 April 2016 at 20:51, Chunyan Zhang <zhang.chunyan@linaro.org> wrote:
>> This patchset adds support for the CoreSight STM IP block.
>
> This has been out there long enough - I'm picking this up.
>
> Alex, I'll have 1/4 go through my tree. Get back to me if you want to
> proceed differently.
Yes, let's keep it that way. I was sure I had it in my tree too, but,
alas, I didn't.
Regards,
--
Alex
prev parent reply other threads:[~2016-04-20 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 2:51 Chunyan Zhang
2016-04-07 2:51 ` [PATCH V5 1/4] stm class: Support devices that override software assigned masters Chunyan Zhang
2016-04-07 2:51 ` [PATCH V5 2/4] coresight: adding path for STM device Chunyan Zhang
2016-04-07 2:51 ` [PATCH V5 3/4] coresight-stm: Bindings for System Trace Macrocell Chunyan Zhang
2016-04-07 2:51 ` [PATCH V5 4/4] coresight-stm: adding driver for CoreSight STM component Chunyan Zhang
2016-04-20 15:06 ` [PATCH V5 0/4] Introduce CoreSight STM support Mathieu Poirier
2016-04-20 17:08 ` Alexander Shishkin [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=87fuug9pi6.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=Michael.Williams@arm.com \
--cc=al.grant@arm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@arm.com \
--cc=nicolas.guion@st.com \
--cc=pratikp@codeaurora.org \
--cc=tor@ti.com \
--cc=zhang.chunyan@linaro.org \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®