From: Suzuki.Poulose@arm.com (Suzuki K Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] coresight: document binding acronyms
Date: Wed, 22 Jun 2016 18:15:58 +0100 [thread overview]
Message-ID: <576AC7CE.6010500@arm.com> (raw)
In-Reply-To: <1466607663-22599-1-git-send-email-mathieu.poirier@linaro.org>
On 22/06/16 16:01, Mathieu Poirier wrote:
> It can be hard for people not familiar with the CoreSight IP blocks
> to make sense of the acronyms found in the current bindings. As such
> this patch expands each acronym in the hope of providing a better
> description of the IP block they represent.
>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Suzuki
WARNING: multiple messages have this Message-ID (diff)
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: sudeep.holla@arm.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] coresight: document binding acronyms
Date: Wed, 22 Jun 2016 18:15:58 +0100 [thread overview]
Message-ID: <576AC7CE.6010500@arm.com> (raw)
In-Reply-To: <1466607663-22599-1-git-send-email-mathieu.poirier@linaro.org>
On 22/06/16 16:01, Mathieu Poirier wrote:
> It can be hard for people not familiar with the CoreSight IP blocks
> to make sense of the acronyms found in the current bindings. As such
> this patch expands each acronym in the hope of providing a better
> description of the IP block they represent.
>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Suzuki
next prev parent reply other threads:[~2016-06-22 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:01 [PATCH V2] coresight: document binding acronyms Mathieu Poirier
2016-06-22 15:01 ` Mathieu Poirier
2016-06-22 15:01 ` Mathieu Poirier
2016-06-22 16:40 ` Sudeep Holla
2016-06-22 16:40 ` Sudeep Holla
2016-06-22 16:40 ` Sudeep Holla
2016-06-22 17:15 ` Suzuki K Poulose [this message]
2016-06-22 17:15 ` Suzuki K Poulose
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=576AC7CE.6010500@arm.com \
--to=suzuki.poulose@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.