From: Varun Sethi <Varun.Sethi@freescale.com>
To: <joro@8bytes.org>, <iommu@lists.linux-foundation.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<stuart.yoder@freescale.com>, <scottwood@freescale.com>,
<alex.williamson@redhat.com>, <r65777@freescale.com>
Cc: Varun Sethi <Varun.Sethi@freescale.com>
Subject: [PATCH 0/3] iommu/fsl: PAMU driver fixes.
Date: Sun, 13 Oct 2013 02:02:31 +0530 [thread overview]
Message-ID: <1381609954-15283-1-git-send-email-Varun.Sethi@freescale.com> (raw)
The first patch fixes a build failure, when we try to build for a Freescale
platform without PCI support.
The second patch enables a default DMA window for the device, once it's
detached from a domain. In case of vfio, once device is detached from a
guest it can be again used by the host.
The last patch adds the maintainer entry for the Freescale PAMU driver.
Varun Sethi (3):
iommu/fsl: Factor out PCI specific code.
iommu/fsl: Enable default DMA window for PCIe devices once detached
Add maintainers entry for the Freescale PAMU driver.
MAINTAINERS | 7 +++
drivers/iommu/fsl_pamu.c | 43 ++++++++++++---
drivers/iommu/fsl_pamu.h | 1 +
drivers/iommu/fsl_pamu_domain.c | 116 +++++++++++++++++++++++++--------------
4 files changed, 117 insertions(+), 50 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-10-12 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 20:32 Varun Sethi [this message]
2013-10-12 20:32 ` [PATCH 1/3] iommu/fsl: Factor out PCI specific code Varun Sethi
2013-10-15 0:16 ` Bjorn Helgaas
2013-10-15 14:35 ` Sethi Varun-B16395
2013-10-12 20:32 ` [PATCH 2/3] iommu/fsl: Enable default DMA window for PCIe devices once detached Varun Sethi
2013-10-12 20:32 ` [PATCH 3/3] Add maintainers entry for the Freescale PAMU driver Varun Sethi
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=1381609954-15283-1-git-send-email-Varun.Sethi@freescale.com \
--to=varun.sethi@freescale.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r65777@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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).