From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Sasha Levin <sashal@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-pci <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Jake Oshins <jakeo@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Dexuan Cui <decui@microsoft.com>
Subject: Re: [PATCH] PCI: pci-hyperv: fix build errors on non-SYSFS config
Date: Wed, 14 Aug 2019 10:58:19 -0500 [thread overview]
Message-ID: <20190814155819.GC253360@google.com> (raw)
In-Reply-To: <20190814101409.GB29414@e121166-lin.cambridge.arm.com>
On Wed, Aug 14, 2019 at 11:14:09AM +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:
>
> [...]
>
> > > > > v3: corrected Fixes: tag [Dexuan Cui <decui@microsoft.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@microsoft.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.
Would you mind picking it up? Then we can sort of keep all the
Hyper-V-related changes together.
next prev parent reply other threads:[~2019-08-14 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 15:53 [PATCH] PCI: pci-hyperv: fix build errors on non-SYSFS config Randy Dunlap
2019-07-12 16:04 ` Haiyang Zhang
2019-07-13 15:03 ` Sasha Levin
2019-07-23 21:21 ` Bjorn Helgaas
2019-08-07 15:06 ` Lorenzo Pieralisi
2019-08-08 1:27 ` Sasha Levin
2019-08-08 10:13 ` Lorenzo Pieralisi
2019-08-14 10:14 ` Lorenzo Pieralisi
2019-08-14 15:58 ` Bjorn Helgaas [this message]
2019-08-15 10:47 ` Lorenzo Pieralisi
2019-08-15 15:14 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190814155819.GC253360@google.com \
--to=helgaas@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jakeo@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).