On Mon, 22 Jan 2024 at 05:31, Tom Rini <tr...@konsulko.com> wrote: > > On Sun, Jan 21, 2024 at 10:41:51PM +0000, Caleb Connolly wrote: > > > > > > On 21/01/2024 15:33, Marek Vasut wrote: > [snip] > > > Assume that there is some large breaking change in Linux 6.(n+1), > > > something which would be problematic for specific U-Boot platform (e.g. > > > i.MX) or would require a lot of work to sort out, will there be a way to > > > temporarily pin DTs for specific platform to older DT version until that > > > is resolved (e.g. pin to 6.n) ? > > > > (Upstream) devicetree has to be forwards and backwards compatible, were such > > a breaking change to get merged without prior discussion with DT users (i.e. > > U-Boot) then I think the correct course of action would be to revert it. > > The caveat is "unless it was wrong before", which happens more often > than is generally thought of I think. I'm not sure off-hand the best way > to deal with that.
I think that's the reason we just want to pull DT at once in the beginning of the next window and allow U-Boot developers/maintainers to detect and fix problems during the full U-Boot release cycle. However, we are open to discussions for a revert if there is a major DT ABI break among Linux major (.0) releases affecting many U-Boot platforms. -Sumit > > -- > Tom