From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Bjorn Helgaas <helgaas@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: Thu, 8 Aug 2019 11:13:54 +0100 [thread overview]
Message-ID: <20190808101354.GA30230@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190808012745.GV17747@sasha-vm>
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
next prev parent reply other threads:[~2019-08-08 10:14 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 [this message]
2019-08-14 10:14 ` Lorenzo Pieralisi
2019-08-14 15:58 ` Bjorn Helgaas
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=20190808101354.GA30230@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=helgaas@kernel.org \
--cc=jakeo@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.