tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: process: maintainer-soc-clean-dts: linux-next is decisive

Devicetree bindings patches go usually via driver subsystem tree, so
obviously testing only SoC branches would result in new dtbs_check
warnings. Mention that linux-next branch is decisice for zero-warnings
rule.

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link: https://lore.kernel.org/r/20250225184822.213296-2-krzysztof.kozlowski@linaro.org
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>

authored by

Krzysztof Kozlowski and committed by
Rob Herring (Arm) a78f7a33 b31cc6af

+3 -2
+3 -2
Documentation/process/maintainer-soc-clean-dts.rst
··· 17 17 No changes to the SoC platform Devicetree sources (DTS files) should introduce 18 18 new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are 19 19 results of issues in an included DTSI file, are considered existing, not new 20 - warnings. The platform maintainers have automation in place which should point 21 - out any new warnings. 20 + warnings. For series split between different trees (DT bindings go via driver 21 + subsystem tree), warnings on linux-next are decisive. The platform maintainers 22 + have automation in place which should point out any new warnings. 22 23 23 24 If a commit introducing new warnings gets accepted somehow, the resulting 24 25 issues shall be fixed in reasonable time (e.g. within one release) or the