From: Mark Brown <broonie@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-spi@vger.kernel.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [RESEND PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML
Date: Tue, 27 Sep 2022 12:59:28 +0100 [thread overview]
Message-ID: <YzLloE/AEdFiHsEj@sirena.org.uk> (raw)
In-Reply-To: <CAMhs-H8664babt9xwE-iCJNCdm+kues-c6V1iPwS63EtdWCV1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On Tue, Sep 27, 2022 at 01:36:04PM +0200, Sergio Paracuellos wrote:
> On Tue, Sep 27, 2022 at 1:12 PM Mark Brown <broonie@kernel.org> wrote:
> > On Tue, Sep 27, 2022 at 05:19:29AM +0200, Sergio Paracuellos wrote:
> > Please submit patches using subject lines reflecting the style for the
> > subsystem, this makes it easier for people to identify relevant patches.
> Since this is a binding migration change I sent the patch expecting
> this going into the devicetree kernel tree. So I just use the common
> device tree change style 'dt-bindings: spi: migrate mt7621 text
> bindings to YAML' as the subject. So I don't really understand what
> you mean above, sorry. What is wrong with this subject? I submitted
> this v3 [0] and I was told by Rob to resend it to you and the
> linux-spi mail list also.
Bindings mostly go through the subsystem rather than the DT tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-27 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 3:19 [RESEND PATCH v3] dt-bindings: spi: migrate mt7621 text bindings to YAML Sergio Paracuellos
2022-09-27 11:12 ` Mark Brown
2022-09-27 11:36 ` Sergio Paracuellos
2022-09-27 11:59 ` Mark Brown [this message]
2022-09-27 12:09 ` Sergio Paracuellos
2022-09-29 16:48 ` Rob Herring
2022-09-29 17:22 ` Sergio Paracuellos
2022-09-27 12:48 ` Mark Brown
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=YzLloE/AEdFiHsEj@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@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;
as well as URLs for NNTP newsgroup(s).