From: Rob Herring <robh@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
arm-soc <arm@kernel.org>,
Device Tree <devicetree@vger.kernel.org>
Subject: Re: [PATCH 00/11] Start converting MVEBU bindings to YAML
Date: Mon, 22 Aug 2022 08:49:33 -0500 [thread overview]
Message-ID: <20220822134933.GC3732690-robh@kernel.org> (raw)
In-Reply-To: <20220820194804.3352415-1-andrew@lunn.ch>
On Sat, Aug 20, 2022 at 09:47:53PM +0200, Andrew Lunn wrote:
> This is the first batch of patches converting the Marvell MVEBU driver
> bindings from .txt to .yaml. So far, kirkwood has been used for
> testing, but these drivers apply to a range of Marvell SoCs.
>
> In order to reduce the number of warnings from the DT schema checking
> tools, a few minor changes have been made to a few DT files. No actual
> errors have been found, the changes just make the checker quiet.
>
> Andrew Lunn (11):
> DT: RTC: orion-rtc: Convert to YAML
> DT: thermal: marvell,kirkwood-thermal: Convert to YAML
> DT: pinctrl: Convert marvell,kirkwood-pintctrl to YAML
> DT: USB: Convert ehci-orion to YAML
> DT: watchdog: Convert marvel.txt to YAML
> arm: DT: kirkwood/orion5: Rename watchdog node
> DT: nand-controller: Reflect reality of marvell,orion-nand
> DT: mtd: Convert orion-nand to YAML
> arm: DT: kirkwood.dtsi: Rename nand to nand-controller
> DT: timer: Convert marvell,orion-timer.txt to YAML
> DT: clock: Convert mvebu-gated-clock.txt to YAML
Please follow naming conventions of the subsystem for the subject.
s/^DT/dt-bindings/
s/YAML/DT schema/
Rob
next prev parent reply other threads:[~2022-08-22 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 19:47 [PATCH 00/11] Start converting MVEBU bindings to YAML Andrew Lunn
2022-08-20 19:47 ` [PATCH 01/11] DT: RTC: orion-rtc: Convert " Andrew Lunn
2022-08-22 20:49 ` Rob Herring
2022-08-22 20:55 ` Rob Herring
2022-08-20 19:47 ` [PATCH 02/11] DT: thermal: marvell,kirkwood-thermal: " Andrew Lunn
2022-08-20 19:47 ` [PATCH 03/11] DT: pinctrl: Convert marvell,kirkwood-pintctrl " Andrew Lunn
2022-08-22 21:16 ` Rob Herring
2022-08-20 19:47 ` [PATCH 04/11] DT: USB: Convert ehci-orion " Andrew Lunn
2022-08-21 20:21 ` Rob Herring
2022-08-20 19:47 ` [PATCH 05/11] DT: watchdog: Convert marvel.txt " Andrew Lunn
2022-08-21 20:21 ` Rob Herring
2022-08-22 0:20 ` Andrew Lunn
2022-08-22 13:47 ` Rob Herring
2022-08-20 19:47 ` [PATCH 06/11] arm: DT: kirkwood/orion5: Rename watchdog node Andrew Lunn
2022-08-20 19:48 ` [PATCH 07/11] DT: nand-controller: Reflect reality of marvell,orion-nand Andrew Lunn
2022-08-21 20:21 ` Rob Herring
2022-08-20 19:48 ` [PATCH 08/11] DT: mtd: Convert orion-nand to YAML Andrew Lunn
2022-08-21 20:21 ` Rob Herring
2022-08-22 0:48 ` Andrew Lunn
2022-08-22 13:43 ` Rob Herring
2022-08-20 19:48 ` [PATCH 09/11] arm: DT: kirkwood.dtsi: Rename nand to nand-controller Andrew Lunn
2022-08-20 19:48 ` [PATCH 10/11] DT: timer: Convert marvell,orion-timer.txt to YAML Andrew Lunn
2022-08-20 19:48 ` [PATCH 11/11] DT: clock: Convert mvebu-gated-clock.txt " Andrew Lunn
2022-08-22 13:49 ` Rob Herring [this message]
2022-08-22 13:53 ` [PATCH 00/11] Start converting MVEBU bindings " Rob Herring
2022-08-22 14:28 ` Andrew Lunn
2022-08-30 18:58 ` Rob Herring
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=20220822134933.GC3732690-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.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).