From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"andrzej.jakowski@linux.intel.com"
<andrzej.jakowski@linux.intel.com>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"Fugate, David" <david.fugate@intel.com>
Subject: Re: [PATCH 0/2] VMD subdevice secondary bus resets
Date: Thu, 19 Nov 2020 18:45:07 +0000 [thread overview]
Message-ID: <2aa5ecc7449c6ae3f203f9ca72a1e1f70c5f235f.camel@intel.com> (raw)
In-Reply-To: <20201119113715.GC19942@e121166-lin.cambridge.arm.com>
On Thu, 2020-11-19 at 11:37 +0000, Lorenzo Pieralisi wrote:
> On Sun, Sep 27, 2020 at 09:05:55PM -0400, Jon Derrick wrote:
> > This set adds some resets for VMD. It's very common code but doesn't
> > seem to fit well anywhere that can also be exported if VMD is built as a
> > module.
> >
> > Jon Derrick (2):
> > PCI: vmd: Reset the VMD subdevice domain on probe
> > PCI: Add a reset quirk for VMD
> >
> > drivers/pci/controller/vmd.c | 32 ++++++++++++++++++++++++
> > drivers/pci/quirks.c | 48 ++++++++++++++++++++++++++++++++++++
> > 2 files changed, 80 insertions(+)
>
> I can queue it up but I need Bjorn's ACK on patch (2).
>
> Lorenzo
I just noticed 2/2 fixes something in 1/2, so I will send a v2 for this
set.
prev parent reply other threads:[~2020-11-19 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 1:05 [PATCH 0/2] VMD subdevice secondary bus resets Jon Derrick
2020-09-28 1:05 ` [PATCH 1/2] PCI: vmd: Reset the VMD subdevice domain on probe Jon Derrick
2020-09-28 1:05 ` [PATCH 2/2] PCI: Add a reset quirk for VMD Jon Derrick
2020-11-19 11:37 ` [PATCH 0/2] VMD subdevice secondary bus resets Lorenzo Pieralisi
2020-11-19 18:45 ` Derrick, Jonathan [this message]
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=2aa5ecc7449c6ae3f203f9ca72a1e1f70c5f235f.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=andrzej.jakowski@linux.intel.com \
--cc=david.fugate@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).