public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	"Marcin Wierzbicki -X (mawierzb - GLOBALLOGIC INC at Cisco)" 
	<mawierzb@cisco.com>, Rob Herring <robh+dt@kernel.org>,
	Daniel Walker <dwalker@fifo99.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: cisco: document the CrayAR compatibles
Date: Thu, 6 Apr 2023 15:15:29 +0000	[thread overview]
Message-ID: <20230406151512.GL40472@zorba> (raw)
In-Reply-To: <6a9f041b-1c35-4691-8451-7119cd05ed17@linaro.org>

On Thu, Apr 06, 2023 at 09:12:34AM +0200, Krzysztof Kozlowski wrote:
> On 06/04/2023 00:30, Daniel Walker wrote:
> > Describe the compatible properties for the Cisco CrayAR SoC.
> > 
> > Cc: xe-linux-external@cisco.com
> > Cc: Marcin Wierzbicki <mawierzb@cisco.com>
> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Cc: Rob Herring <robh+dt@kernel.org>
> 
> Please drop the autogenerated scripts/get_maintainer.pl CC-entries from
> commit msg. There is no single need to store automated output of
> get_maintainers.pl in the git log. It can be easily re-created at any
> given time, thus its presence in the git history is redundant and
> obfuscates the log.
> 
> If you need it for your own patch management purposes, keep it under the
> --- separator.
 
I added these, so it's not script output. I can move them under the separator.
The reason for that was to make sure people who commented get Cc'd.

> > Signed-off-by: Daniel Walker <dwalker@fifo99.com>
> > ---
> >  .../devicetree/bindings/arm/cisco/crayar.yaml | 27 +++++++++++++++++++
> >  1 file changed, 27 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/arm/cisco/crayar.yaml
> > 
> > diff --git a/Documentation/devicetree/bindings/arm/cisco/crayar.yaml b/Documentation/devicetree/bindings/arm/cisco/crayar.yaml
> > new file mode 100644
> > index 000000000000..0ee4e6313ab0
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/cisco/crayar.yaml
> 
> How many (or not many) platforms do you expect from Cisco? We mostly
> have one file per SoC manufacturer.

We have two SoC's one called CrayAR and another called Craw. I've submitted the
Craw dts file before , but I've not resubmitted it. Under Craw I think we have
at least two, but more likely five variations. CrayAR we have one variation with
at least one more planned.

So we would plan over time to add two dtsi files and three to four dts files to
this directory. Then more over time.

Daniel

  reply	other threads:[~2023-04-06 15:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 22:30 [PATCH v2 2/2] dt-bindings: cisco: document the CrayAR compatibles Daniel Walker
2023-04-06  7:12 ` Krzysztof Kozlowski
2023-04-06 15:15   ` Daniel Walker (danielwa) [this message]
2023-04-06 16:50     ` Krzysztof Kozlowski
2023-04-06 18:32       ` Daniel Walker (danielwa)
2023-04-06 18:56         ` Krzysztof Kozlowski
2023-04-06 19:15           ` Daniel Walker (danielwa)
2023-04-07  6:51             ` Krzysztof Kozlowski
2023-04-07 15:15               ` Daniel Walker (danielwa)
2023-04-07 16:04   ` Daniel Walker (danielwa)
2023-04-10 15:28     ` Krzysztof Kozlowski
2023-04-10 17:09       ` Daniel Walker (danielwa)
2023-04-10 17:51         ` Daniel Walker (danielwa)
2023-04-12  7:24           ` Krzysztof Kozlowski
2023-04-12 15:04             ` Daniel Walker (danielwa)
2023-04-12 16:13               ` Krzysztof Kozlowski
2023-04-12 17:01                 ` Daniel Walker (danielwa)
2023-04-12 17:18                   ` Krzysztof Kozlowski
2023-04-12 18:51                     ` Daniel Walker (danielwa)
2023-04-12 13:50 ` Rob Herring
2023-04-12 15:05   ` Daniel Walker (danielwa)

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=20230406151512.GL40472@zorba \
    --to=danielwa@cisco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwalker@fifo99.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mawierzb@cisco.com \
    --cc=robh+dt@kernel.org \
    --cc=xe-linux-external@cisco.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