[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190814101409.GB29414@e121166-lin.cambridge.arm.com>
Date: Wed, 14 Aug 2019 11:14:09 +0100
From: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Sasha Levin <sashal@...nel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Randy Dunlap <rdunlap@...radead.org>,
linux-pci <linux-pci@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Matthew Wilcox <willy@...radead.org>,
Jake Oshins <jakeo@...rosoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Dexuan Cui <decui@...rosoft.com>
Subject: Re: [PATCH] PCI: pci-hyperv: fix build errors on non-SYSFS config
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:
[...]
> > > > v3: corrected Fixes: tag [Dexuan Cui <decui@...rosoft.com>]
> > > > This is the Microsoft-preferred version of the patch.
> > > >
> > > > drivers/pci/Kconfig | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > --- lnx-52.orig/drivers/pci/Kconfig
> > > > +++ lnx-52/drivers/pci/Kconfig
> > > > @@ -181,7 +181,7 @@ config PCI_LABEL
> > > >
> > > > config PCI_HYPERV
> > > > tristate "Hyper-V PCI Frontend"
> > > > - depends on X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN
> > > > && X86_64
> > > > + depends on X86_64 && HYPERV && PCI_MSI &&
> > > > PCI_MSI_IRQ_DOMAIN && SYSFS
> > > > help
> > > > The PCI device frontend driver allows the kernel to import arbitrary
> > > > PCI devices from a PCI backend to support PCI driver domains.
> > > >
> > >
> > > Reviewed-by: Haiyang Zhang <haiyangz@...rosoft.com>
> >
> > 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.
Bjorn please let me know if you can pick this up or I should, thanks.
Lorenzo
> Does this need to be tagged for stable? a15f2c08c708 appeared in
> v4.19, so my first guess is that it's not stable material.
>
> Bjorn
Powered by blists - more mailing lists