linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: "myron.stowe@redhat.com" <myron.stowe@redhat.com>,
	"hch@lst.de" <hch@lst.de>,
	"helgaas@kernel.org" <helgaas@kernel.org>,
	"Bauer, Scott" <scott.bauer@intel.com>,
	"jroedel@suse.de" <jroedel@suse.de>,
	"Fugate, David" <david.fugate@intel.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"Busch, Keith" <keith.busch@intel.com>
Subject: Re: [PATCH 0/5] Enable an additional VMD device id
Date: Thu, 24 May 2018 16:36:48 +0000	[thread overview]
Message-ID: <1527179806.8026.1.camel@intel.com> (raw)
In-Reply-To: <20180524163420.GA24940@e107981-ln.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

On Thu, 2018-05-24 at 17:34 +0100, Lorenzo Pieralisi wrote:
> On Thu, May 24, 2018 at 04:15:08PM +0000, Derrick, Jonathan wrote:
> > Hi Lorenzo,
> > 
> > On Thu, 2018-05-24 at 12:44 +0100, Lorenzo Pieralisi wrote:
> > > On Fri, May 18, 2018 at 01:27:57PM -0600, Jon Derrick wrote:
> > > > This patchset enables an additional VMD device ID to the VMD
> > > > driver
> > > > supporting assignment of the membar addresses from shadow
> > > > registers
> > > > and
> > > > allows more flexibility in assigning bus numbers to a VMD PCIe
> > > > domain.
> > > > Additional VMD root port device ids have been added to the VMD
> > > > AER
> > > > quirk.
> > > > 
> > > > Changes from rfc include comments, code structure, and using
> > > > pci_add_resource_offset to correctly assign addresses while
> > > > virtualized.
> > > > 
> > > > Applies to Bjorn's next branch
> > > 
> > > Hi Jon,
> > > 
> > > You should base it on v4.17-rc1 and if there is a dependency on
> > > later -rc* or a branch in Bjorn/my queue please let us know.
> > 
> > It looks like it applies cleanly to 4.17-rc1 and rc6.
> > 
> > > > Jon Derrick (5):
> > > >   PCI: Add Intel VMD devices to pci ids
> > > >   PCI/VMD: Assign membar addresses from shadow registers
> > > >   PCI/VMD: Add offset to bus numbers if necessary
> > > >   x86/PCI: Add additional VMD device root ports to VMD AER
> > > > quirk
> > > >   PCI/VMD: Add an additional VMD device id to driver device id
> > > > table
> > > > 
> > > >  arch/x86/pci/fixup.c    |  4 +++
> > > >  drivers/pci/host/vmd.c  | 91
> > > > +++++++++++++++++++++++++++++++++++++++++++------
> > > >  include/linux/pci_ids.h |  2 ++
> > > >  3 files changed, 87 insertions(+), 10 deletions(-)
> > > 
> > > I need Bjorn's ACK on patch (4), or if Bjorn is keen on pulling
> > > the
> > > series, here's mine on the series:
> > > 
> > > Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > 
> > Would you like me to rebase it and resend with Bjorn's ack?
> 
> No need to resend but I need Bjorn's ACK on patch (4) in order to
> queue it.
> 
> Thanks,
> Lorenzo

Here's Bjorn's ack since you may not have it seen it yet:
https://patchwork.ozlabs.org/patch/916565/


Thanks,
Jon

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3278 bytes --]

  reply	other threads:[~2018-05-24 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 19:27 [PATCH 0/5] Enable an additional VMD device id Jon Derrick
2018-05-18 19:27 ` [PATCH 1/5] PCI: Add Intel VMD devices to pci ids Jon Derrick
2018-05-18 19:27 ` [PATCH 2/5] PCI/VMD: Assign membar addresses from shadow registers Jon Derrick
2018-05-18 19:28 ` [PATCH 3/5] PCI/VMD: Add offset to bus numbers if necessary Jon Derrick
2018-05-18 19:28 ` [PATCH 4/5] x86/PCI: Add additional VMD device root ports to VMD AER quirk Jon Derrick
2018-05-24 13:37   ` Bjorn Helgaas
2018-05-18 19:28 ` [PATCH 5/5] PCI/VMD: Add an additional VMD device id to driver device id table Jon Derrick
2018-05-24 11:44 ` [PATCH 0/5] Enable an additional VMD device id Lorenzo Pieralisi
2018-05-24 16:15   ` Derrick, Jonathan
2018-05-24 16:34     ` Lorenzo Pieralisi
2018-05-24 16:36       ` Derrick, Jonathan [this message]
2018-05-24 16:58         ` Lorenzo Pieralisi

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=1527179806.8026.1.camel@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=david.fugate@intel.com \
    --cc=hch@lst.de \
    --cc=helgaas@kernel.org \
    --cc=jroedel@suse.de \
    --cc=keith.busch@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=myron.stowe@redhat.com \
    --cc=scott.bauer@intel.com \
    /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).