From: Jon Derrick <jonathan.derrick@intel.com>
To: linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org
Cc: Bjorn Helgaas <helgaas@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Keith Busch <keith.busch@intel.com>,
Scott Bauer <scott.bauer@intel.com>,
David Fugate <david.fugate@intel.com>,
linux-kernel@vger.kernel.org,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [PATCH v2 0/4] VMD fixups
Date: Thu, 17 Aug 2017 12:10:10 -0600 [thread overview]
Message-ID: <20170817181014.1257-1-jonathan.derrick@intel.com> (raw)
Mostly just cleanup in this revision, eg, trying to limit scope of vmd code to
x86
Previous:
https://patchwork.kernel.org/patch/9886095/
https://patchwork.kernel.org/patch/9886097/
https://patchwork.kernel.org/patch/9886101/
Jon Derrick (4):
MAINTAINERS: Add Jonathan Derrick as VMD maintainer
pci/x86: Move VMD quirks to x86 fixups
x86/PCI: Use is_vmd rather than relying on the domain number
iommu: Prevent VMD child devices from being remapping targets
MAINTAINERS | 1 +
arch/x86/pci/fixup.c | 18 ++++++++++++++++++
drivers/iommu/intel-iommu.c | 5 +++++
drivers/pci/quirks.c | 17 -----------------
4 files changed, 24 insertions(+), 17 deletions(-)
--
2.9.4
next reply other threads:[~2017-08-17 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 18:10 Jon Derrick [this message]
[not found] ` <20170817181014.1257-1-jonathan.derrick-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-08-17 18:10 ` [PATCH v2 1/4] MAINTAINERS: Add Jonathan Derrick as VMD maintainer Jon Derrick
2017-08-17 18:10 ` [PATCH v2 3/4] x86/PCI: Use is_vmd rather than relying on the domain number Jon Derrick
2017-08-30 19:23 ` [PATCH v2 0/4] VMD fixups Bjorn Helgaas
2017-08-17 18:10 ` [PATCH v2 2/4] pci/x86: Move VMD quirks to x86 fixups Jon Derrick
2017-08-17 18:10 ` [PATCH v2 4/4] iommu: Prevent VMD child devices from being remapping targets Jon Derrick
[not found] ` <20170817181014.1257-5-jonathan.derrick-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-08-18 16:04 ` Bjorn Helgaas
2017-08-18 16:35 ` Robin Murphy
2017-08-24 16:02 ` Bjorn Helgaas
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=20170817181014.1257-1-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=david.fugate@intel.com \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).