On Fri, 1 Oct 2021 at 10:44, Daniel P. Berrangé <berra...@redhat.com> wrote: > On Fri, Oct 01, 2021 at 10:37:51AM +0100, Peter Maydell wrote: > > I agree in general, but (per the commit message here) our dtc > > submodule is currently pointing at some random not-a-release > > commit in upstream dtc. We should at least move forward to > > whatever the next released dtc after that is, before we say > > "no more dtc updates". > > Yep, if we want to fix it onto an official version tag, that's > OK, just not jumping right to very latest version. We might want > to move it backwards to better align with what we're targetting > in the support
The reason for the last update to the dtc submodule was not for any specific external API requirement, but in order to get a change we needed to get it to build more cleanly when building it as a submodule (QEMU commit 67953a379e). To not regress that, we need upstream dtc commit 85e5d839847a. The next published dtc release after that commit is v1.6.1, which is what this submodule update patch proposes moving to. -- PMM
