Re: [PATCH 0/7] dt-bindings: restrict node name suffixes
Conor Dooley <[email protected]> Tue, 30 May 2023 18:11:06 +0100
| Newsgroups | dev.linux.lists.timestamp,org.alsa-project.alsa-devel,org.infradead.lists.linux-phy,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pwm,org.kernel.vger.linux-rtc,org.kernel.vger.linux-spi,org.kernel.vger.linux-watchdog |
|---|---|
| Message-ID | <20230530-banister-luxurious-d33a5d289749@spud> |
On Tue, May 30, 2023 at 04:48:44PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Tree-wide cleanup of DTS node name suffixes "-N", e.g. "pwm-5", so we allow > only decimal numbers. In few cases narrow the pattern to also disallow > multiple suffixes, e.g. "pwm-5-5". I figure there'll be quite a bit of stuff to fix up afterwards? Reviewed-by: Conor Dooley <[email protected]> Thanks, Conor. > > No dependencies, can be applied by individual subsystems. > > Cc: Tony Lindgren <[email protected]> > Cc: Oleksij Rempel <[email protected]> > > Link: https://lore.kernel.org/all/[email protected]/ > > Best regards, > Krzysztof > > Krzysztof Kozlowski (7): > dt-bindings: phy: intel,combo-phy: restrict node name suffixes > dt-bindings: pwm: restrict node name suffixes > dt-bindings: rtc: restrict node name suffixes > dt-bindings: slimbus: restrict node name suffixes > spi: dt-bindings: restrict node name suffixes > dt-bindings: timestamp: restrict node name suffixes > dt-bindings: watchdog: restrict node name suffixes > > Documentation/devicetree/bindings/phy/intel,combo-phy.yaml | 2 +- > Documentation/devicetree/bindings/pwm/pwm.yaml | 2 +- > Documentation/devicetree/bindings/rtc/rtc.yaml | 2 +- > Documentation/devicetree/bindings/slimbus/slimbus.yaml | 2 +- > Documentation/devicetree/bindings/spi/spi-controller.yaml | 2 +- > .../bindings/timestamp/hardware-timestamps-common.yaml | 2 +- > Documentation/devicetree/bindings/watchdog/watchdog.yaml | 4 ++-- > 7 files changed, 8 insertions(+), 8 deletions(-) > > -- > 2.34.1 >
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZHYuKgAKCRB4tDGHoIJi 0nXKAQDamcvDwarCjeG65qUN+fBYxaI+//cyJEQB1SuuBpUTGgEAy0ivPKjui6wX d/shbUIhWWfohF1w8yRNuYfQATp+AAQ= =EmEg -----END PGP SIGNATURE-----