All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: will@kernel.org, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [PATCH 1/4] dt-bindings: perf: marvell: cn10k ddr performance monitor
Date: Thu, 29 Jul 2021 17:29:46 -0600	[thread overview]
Message-ID: <YQM56mlxM19UDu93@robh.at.kernel.org> (raw)
In-Reply-To: <20210726091027.798-2-bbhushan2@marvell.com>

On Mon, Jul 26, 2021 at 02:40:24PM +0530, Bharat Bhushan wrote:
> Add binding documentation for the Marvell CN10k DDR
> performance monitor unit.
> 
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
> ---
>  .../bindings/perf/marvell-cn10k-ddr.txt           | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/perf/marvell-cn10k-ddr.txt

Bindings are in DT schema format now.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: will@kernel.org, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [PATCH 1/4] dt-bindings: perf: marvell: cn10k ddr performance monitor
Date: Thu, 29 Jul 2021 17:29:46 -0600	[thread overview]
Message-ID: <YQM56mlxM19UDu93@robh.at.kernel.org> (raw)
In-Reply-To: <20210726091027.798-2-bbhushan2@marvell.com>

On Mon, Jul 26, 2021 at 02:40:24PM +0530, Bharat Bhushan wrote:
> Add binding documentation for the Marvell CN10k DDR
> performance monitor unit.
> 
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
> ---
>  .../bindings/perf/marvell-cn10k-ddr.txt           | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/perf/marvell-cn10k-ddr.txt

Bindings are in DT schema format now.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-29 23:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26  9:10 [PATCH 0/4] cn10k DDR Performance monitor support Bharat Bhushan
2021-07-26  9:10 ` Bharat Bhushan
2021-07-26  9:10 ` [PATCH 1/4] dt-bindings: perf: marvell: cn10k ddr performance monitor Bharat Bhushan
2021-07-26  9:10   ` Bharat Bhushan
2021-07-29 23:29   ` Rob Herring [this message]
2021-07-29 23:29     ` Rob Herring
2021-08-03 11:38     ` [EXT] " Bharat Bhushan
2021-08-03 11:38       ` Bharat Bhushan
2021-07-26  9:10 ` [PATCH 2/4] perf/marvell: ADD cn10k DDR PMU basic support Bharat Bhushan
2021-07-26  9:10   ` Bharat Bhushan
2021-07-26  9:10 ` [PATCH 3/4] perf/marvell: cn10k DDR perfmon event overflow handling Bharat Bhushan
2021-07-26  9:10   ` Bharat Bhushan
2021-07-26  9:10 ` [PATCH 4/4] perf/marvell: cn10k DDR perf event core ownership Bharat Bhushan
2021-07-26  9:10   ` Bharat Bhushan

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=YQM56mlxM19UDu93@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bbhushan2@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sgoutham@marvell.com \
    --cc=will@kernel.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.