On Fri, May 22, 2026 at 9:17 AM Lorenzo Stoakes <[email protected]> wrote: > > On Fri, May 22, 2026 at 09:07:29AM -0600, Nico Pache wrote: > > Whoops I manually changed the coverletter subject to reflect that this > > in on mm-hotfixes-unstable but never updated the others... > > > > Hopefully that is ok. Just a small mistake. Base commit is referenced here. > > It's not ok, this isn't suitable for a hotfix in any way shape or form? > > As you know, because we told you :) May has been difficult because of > conferences, holidays (and in my case burnout recovery). > > And unfortunately the series seems to have needed quite a bit of review again > (my suggestion to you would be to ensure you don't make major changes, only > small incremental ones on the basis of review feedback). > > So this isn't viable for 7.2, and we'll have to target 7.3. Therefore there > was no rush. > > Also please don't spring a respin on this series on us without discussion > first, with people away and (frankly) the amount of work involved here, > you're going to have to accept the pace that workload/availability permits. > > Adding spurious hotfixes tags doesn't help anything :) please don't do that > again.
Hi, Sorry for the confusion but Andrew and I spoke about this before I sent it, and he confirmed that I should send it against this tree to prevent merge conflicts. Because Zi's series depends on this, and this is already in the mm tree, choosing a candidate before my commits was best to prevent merge conflicts. The intent wasn't that this is a hotfix, just that this was the closest base before the v17 that is already in the tree. Sorry for the confusion, hopefully Andrew can still apply it to the correct tree. -- Nico > > Thanks, Lorenzo >
