[PATCH 1/1] Squashed 'dts/upstream/' changes from b35b9bd1d4ee..7e08733c96c8

[Jonas Karlman]

Hi Tom,

On 2024-05-14 18:42, Tom Rini wrote:> 
> git-subtree-dir: dts/upstream
> git-subtree-split: 7e08733c96c84eb323f47e9b248c924e2ac6272a
> ---
> This moves OF_UPSTREAM to be tracking the v6.9 release and is for the
> -next branch. To test these changes yourself locally, either use my
> "WIP/14May2024-next" branch or run:
> ./dts/update-dts-subtree.sh pull v6.9-dts
> yourself locally. I intend to wait a few days to apply this to -next, to
> give people time to test.
> 

There are currently more boards/SoCs that use OF_UPSTREAM in master
branch than in next branch, a few Rockchip SoCs and other boards/SoCs.
Next dts/upstream sync will probably be good to do together with a merge
of master into next :-)

Also what is the expected sync cadence of dts/upstream? Linux v6.10 will
probably be released shortly after U-Boot v2024.07. So will next sync be
to v6.10-dts if that happens in the U-Boot merge window or do we expect
2024.10 to use v6.9 DTs if the v6.10 release gets delayed and miss the
U-Boot merge window?

Linux kernel typically have all major DT changes in -rc1 and fixes in
later -rcX, so for next branch I would suggest an early sync to a
v6.10-rcX-dts tag, and then sync to the final v6.10-dts tag once v6.10
gets released. That should give more time for testing, migration and
cleanup using v6.10 DTs in time for a 2024.10 release.

Regards,
Jonas