Effectively all Tesla FSD and Google GS101 DTS patches go via Samsung SoC maintainer, who applies the same rules as for Samsung SoC: DTS must be fully DT bindings compliant (`dtbs_check W=1`). Existing sources already are compliant, so just document that implicit rule by mentioning respective maintainer profile in their entries. Cc: Peter Griffin <peter.griffin@xxxxxxxxxx> Cc: André Draszik <andre.draszik@xxxxxxxxxx> Cc: Tudor Ambarus <tudor.ambarus@xxxxxxxxxx> Cc: Alim Akhtar <alim.akhtar@xxxxxxxxxxx> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index efba8922744a..4073f7ac978f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3392,6 +3392,7 @@ M: linux-fsd@xxxxxxxxx L: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx (moderated for non-subscribers) L: linux-samsung-soc@xxxxxxxxxxxxxxx S: Maintained +P: Documentation/process/maintainer-soc-clean-dts.rst F: arch/arm64/boot/dts/tesla/ ARM/TEXAS INSTRUMENT AEMIF/EMIF DRIVERS @@ -10317,6 +10318,7 @@ R: Tudor Ambarus <tudor.ambarus@xxxxxxxxxx> L: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx (moderated for non-subscribers) L: linux-samsung-soc@xxxxxxxxxxxxxxx S: Maintained +P: Documentation/process/maintainer-soc-clean-dts.rst C: irc://irc.oftc.net/pixel6-kernel-dev F: Documentation/devicetree/bindings/clock/google,gs101-clock.yaml F: Documentation/devicetree/bindings/soc/google/google,gs101-pmu-intr-gen.yaml -- 2.43.0
