Merging ======= I propose to take entire patchset through my tree (Samsung SoC), because: 1. I already took similar work this cycle: https://lore.kernel.org/all/169997520487.6747.17671551558724027958.b4-ty@xxxxxxxxxx/ 2. Two new SoCs are coming (Google GS101 and ExynosAutov920) and they might touch the same lines. It is reasonable for me to take the bindings for the new SoCs, to have clean `make dtbs_check` on the new DTS. 3. Having it together helps me to have clean `make dtbs_check` within my tree on the existing DTS. 4. No drivers are affected by this change. If folks agree, please kindly Ack the patches. Description =========== See: https://lore.kernel.org/all/20231108104343.24192-1-krzysztof.kozlowski@xxxxxxxxxx/ Best regards, Krzysztof Krzysztof Kozlowski (6): dt-bindings: i2c: exynos5: add specific compatible for Tesla FSD dt-bindings: pwm: samsung: add specific compatible for Tesla FSD dt-bindings: serial: samsung: add specific compatible for Tesla FSD dt-bindings: samsung: exynos-pmu: add specific compatible for Tesla FSD dt-bindings: watchdog: samsung: add specific compatible for Tesla FSD arm64: dts: fsd: add specific compatibles for Tesla FSD .../devicetree/bindings/i2c/i2c-exynos5.yaml | 1 + .../devicetree/bindings/pwm/pwm-samsung.yaml | 1 + .../bindings/serial/samsung_uart.yaml | 1 + .../bindings/soc/samsung/exynos-pmu.yaml | 1 + .../bindings/watchdog/samsung-wdt.yaml | 21 +++++++----- arch/arm64/boot/dts/tesla/fsd.dtsi | 32 +++++++++---------- 6 files changed, 33 insertions(+), 24 deletions(-) -- 2.34.1
