On Fri, 19 Jul 2024 11:52:00 +0100 Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx> wrote: > > > It's really big and it's quite new and it's really late. I think it best to await the > > > next -rc cycle, see how much grief it all causes. > > > > Yes, this patch set is huge. > > > > It is, however, extremely necessary to get to the point where we can > > test things better than full system tests (and then wait for a distro to > > rebuild all their rpms and find a missed issue). I know a lot of people > > would rather see everything in a kunit test, but the reality is that, at > > this level in the kernel, we cannot test as well as we can with the > > userspace approach. > > > > With the scope of the change, it will be a lot of work to develop in > > parallel and rebase on top of the moving of this code. I'm wondering if > > you can provide some more information on your plan? Will this be the > > first series in your mm-unstable branch after the release? iow, should I > > be developing on top of the code moving around for my future work? I am > > happy enough to rebase my in-flight MAP_FIXED patches on top of this set > > if that helps things along. > > > > Thanks, > > Liam > > Thanks Liam! > > I think best way forward unless you feel we should take a different > approach Andrew is for me to simply wait until the end of the merge window > and at the start of the week after rebase on 6.11-rc1 and do a resend? How about you send out a version early next week and I'll aim to send it in to Linus late in this merge window?
