On Mon, Feb 24, 2020 at 01:23:46PM +0100, Petr Mladek wrote: > On Mon 2020-02-24 11:09:49, Andy Shevchenko wrote: > > On Tue, Feb 18, 2020 at 09:58:44AM +0100, Petr Mladek wrote: > > > On Mon 2020-02-17 13:40:10, Andy Shevchenko wrote: > > > > This is third version to get rid of problematic DMA and PM calls in > > > > the serial kernel console code. > > > > > > > > Patches 1, 3 and 4 are preparatory ones. > > > > > > > > After previous discussion Tony suggested to add a possibility to detach > > > > and attach back kernel console from user space. It's done in the patch 2. > > > > > > > > Note, it depends to recently submitted and applied patches in > > > > the core console code [2, 3]. Petr, may you confirm that [3] is > > > > immutable or even send Greg KH a PR? > > > > > > Yes, the branch for-5.7-console-exit in printk.git is basically > > > immutable. I do my best to prevent rebasing. > > > > Thanks for confirming this! > > > > Greg, thanks for applying patches 1, 3, and 4. How can we proceed from this point? > > > > > > Greg, see above note before applying, thanks! > > The easiest solution would be when all patches go via one tree. > > Greg, would you want to take the 7 patches from > https://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git/log/?h=for-5.7-console-exit > via your tree? I think it would be nice to send formal PR to Greg. > I have never done such shuffles between two maintainer trees. > Are there any preferred steps how to do so smoothly, please? Usually it's done via immutable branch / tag that all stakeholders (including the initiator) can pull into their -next branches. In any case, if Greg is considering next cycle, don't forget to apply this to your -next :-) (I think it's already there) -- With Best Regards, Andy Shevchenko
