On 13/02/2023 12:57, Janne Grunau wrote: > On 2023-02-13 12:10:36 +0100, Krzysztof Kozlowski wrote: >> On 12/02/2023 16:41, Janne Grunau wrote: >>> The block on Apple M2 SoCs is compatible with the existing driver so >>> just add its per-SoC compatible. >>> >>> Signed-off-by: Janne Grunau <j@xxxxxxxxxx> >>> >>> --- >>> This trivial dt-bindings update should be merged through the asahi-soc >>> tree to ensure validation of the Apple M2 (t8112) devicetrees in this >>> series. >> >> No, the bindings go via subsystem. Just because you want to validate >> something is not really a reason - you can validate on next. Don't >> create special rules for Asahi... or rather - why Asahi is special than >> everyone else? > > We did that 2 or 3 times in the past without commnts that it is not > desired so I wasn't aware that this would be special handling. > > Merging binding and devicetree updates together looks to me like the > most sensible option since dtbs validation is the only testable > dependecy of dt binding updates. > Keeping them together ensures the dtbs validate without delaying > devicetree changes by one kernel release after the dt-bindings change > was merged. > I suppose it works out most of the time if the merge request is sent > only if it validates in next. That still depends on the merge order in > the merge window but -rc1 should be fine. BTW, your approach causes also bisectability with checkpatch on the drivers or the delay of drivers... Therefore not much solved here. Best regards, Krzysztof
