From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Rob Herring <robh@kernel.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
devicetree@vger.kernel.org, "Marek Behún" <kabel@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Mark Brown" <broonie@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Pratyush Yadav" <p.yadav@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: bus: moxtet: Fix reference to SPI peripheral DT properties
Date: Tue, 31 Jan 2023 21:52:52 +0100 [thread overview]
Message-ID: <Y9l/pGzBCgWcLR2w@probook> (raw)
In-Reply-To: <20230130221626.GA3618337-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Mon, Jan 30, 2023 at 04:16:26PM -0600, Rob Herring wrote:
> On Sun, Jan 29, 2023 at 01:35:53PM +0100, Jonathan Neuschäfer wrote:
> > spi-bus.txt has been converted to YAML and the peripheral properties
> > have been moved to spi-controller.yaml.
> >
> > Fixes: 0a1b929356830 ("spi: Add YAML schemas for the generic SPI options")
> > Fixes: 8762b07c95c18 ("spi: dt-bindings: add schema listing peripheral-specific properties")
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> > ---
> > Documentation/devicetree/bindings/bus/moxtet.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> I'm not really interested in fixes to .txt bindings. Fix it by
> converting to schema if you want to.
Fair enough.
> By my count, there's 37 other cases, why just this one?
Mainly because a patch to a large number of files seemed harder to
coordinate well.
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-31 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 12:35 [PATCH] dt-bindings: bus: moxtet: Fix reference to SPI peripheral DT properties Jonathan Neuschäfer
2023-01-29 12:57 ` Marek Behún
2023-01-30 22:16 ` Rob Herring
2023-01-31 20:52 ` Jonathan Neuschäfer [this message]
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=Y9l/pGzBCgWcLR2w@probook \
--to=j.neuschaefer@gmx.net \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=p.yadav@ti.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox