From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: devicetree@vger.kernel.org, tsbogend@alpha.franken.de,
krzysztof.kozlowski+dt@linaro.org, arinc.unal@arinc9.com
Subject: Re: [PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML
Date: Mon, 26 Sep 2022 13:28:48 -0500 [thread overview]
Message-ID: <20220926182848.GA2523250-robh@kernel.org> (raw)
In-Reply-To: <2b5b2937-45ae-42dd-1d96-115898eb9c7f@linaro.org>
On Wed, Sep 21, 2022 at 09:29:00AM +0200, Krzysztof Kozlowski wrote:
> On 21/09/2022 09:28, Sergio Paracuellos wrote:
> > SoC MT7621 SPI bindings used text format, so migrate them to YAML.
> > There are some additions to the binding that were not in the original
> > file. This binding is used in MT7621 and MT7628a Ralink SoCs. To
> > properly match both dts nodes in tree we need to add to the schema
> > 'clocks', 'clock-names' and 'reset-names'. Both 'clock-names' and
> > 'reset-names' use 'spi' as string so maintain that as const in
> > the schema.
> >
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > ---
> > Changes in v3:
> > - Add Krzysztof's Reviewed-by tag.
>
> There's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
But not when they aren't Cc'ed. Please resend to Mark B and linux-spi.
Rob
next prev parent reply other threads:[~2022-09-26 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:28 [PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML Sergio Paracuellos
2022-09-21 7:29 ` Krzysztof Kozlowski
2022-09-21 7:31 ` Sergio Paracuellos
2022-09-26 18:28 ` Rob Herring [this message]
2022-09-27 3:21 ` Sergio Paracuellos
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=20220926182848.GA2523250-robh@kernel.org \
--to=robh@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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.