On Wed, Aug 07, 2019 at 09:27:45PM -0400, Sasha Levin wrote: > On Wed, Aug 07, 2019 at 04:06:54PM +0100, Lorenzo Pieralisi wrote: > > On Tue, Jul 23, 2019 at 04:21:07PM -0500, Bjorn Helgaas wrote: > > > On Sat, Jul 13, 2019 at 11:03:53AM -0400, Sasha Levin wrote: > > > > Queued up for hyperv-fixes, thank you! > > > > > > What merge strategy do you envision for this? Previous > > > drivers/pci/controller/pci-hyperv.c changes have generally been merged > > > by Lorenzo and incorporated into my PCI tree. > > > > > > This particular patch doesn't actually touch pci-hyperv.c; it touches > > > drivers/pci/Kconfig, so should somehow be coordinated with me. > > > > > > Does this need to be tagged for stable? a15f2c08c708 appeared in > > > v4.19, so my first guess is that it's not stable material. > > > > AFAIC Bjorn's question still stands. Who will pick this patch up ? > > Would it be easier if I just ignored Hyper-V PCI patches? I think it probably would, yes. Actually this patch does not even fall within "Hyper-V CORE AND DRIVERS" maintainers entry. As for drivers/pci/controller/pci-hyperv.c, for urgent fixes I understand it is easier for you to pull them I would still ask you please to sync with me before pulling them. Thanks, Lorenzo
