On Mon, 2023-05-22 at 13:29 +0200, Arnd Bergmann wrote: > On Mon, May 22, 2023, at 12:50, Niklas Schnelle wrote: > > > A few patches have already been applied but I've kept those which are not yet > > in v6.4-rc3. > > > > This version is based on v6.4-rc3 and is also available on my kernel.org tree > > in the has_ioport_v5: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/niks/linux.git > > I think it would be best if as many patches as possible get merged > into v6.5 through the individidual subsystems, though I can take > whatever is left through the asm-generic tree. > > Since the goal is to have maintainers pick up part of this, I would > recommend splitting the series per subsystem, having either a > separate patch or a small series for each maintainer that should > pick them up. > > More importantly, I think you should rebase the series against > linux-next in order to find and drop the patches that are queued > up for 6.5 already. The patches will be applied into branches > that are based on 6.4-rc of course, but basing on linux-next > is usually the easiest when targeting multiple maintainer > trees. > > Maybe let's give it another week to have more maintainers pick > up stuff from v5, and then send out a v6 as separate submissions. > > Arnd Hi Arnd and All, I'm sorry there hasn't been an updated in a long time and we're missing v6.5. I've been quite busy with other work and life. Speaking of, I will be mostly out for around a month starting some time mid to end July as, if all goes well, I'm expecting to become a dad. That said, I haven't forgotten about this and your overall plan of sending per- subsystem patches sounds good, just haven't had the time to also incorporate the feedback. Thanks, Niklas
