From: Joerg Roedel <joro@8bytes.org>
To: Varun Sethi <Varun.Sethi@freescale.com>
Cc: iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org,
galak@kernel.crashing.org, alex.williamson@redhat.com,
stuart.yoder@freescale.com, scottwood@freescale.com
Subject: Re: [PATCH 1/3] powerpc: Add iommu domain pointer to device archdata
Date: Wed, 14 Aug 2013 11:48:03 +0200 [thread overview]
Message-ID: <20130814094802.GC4491@8bytes.org> (raw)
In-Reply-To: <1373863857-27239-1-git-send-email-Varun.Sethi@freescale.com>
On Mon, Jul 15, 2013 at 10:20:55AM +0530, Varun Sethi wrote:
> Add an iommu domain pointer to device (powerpc) archdata. Devices
> are attached to iommu domains and this pointer provides a mechanism
> to correlate between a device and the associated iommu domain. This
> field is set when a device is attached to a domain.
>
> Signed-off-by: Varun Sethi <Varun.Sethi@freescale.com>
> Acked-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> - rebased patch to 3.11-rc1
> arch/powerpc/include/asm/device.h | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
Okay, I applied these patches to my ppc/pamu branch. But before I merge
it to my next branch (so that it can go upstream) I want to have a
compile-test-case first. Can you send me a working .config which
includes this driver?
Thanks,
Joerg
next prev parent reply other threads:[~2013-08-14 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 4:50 [PATCH 1/3] powerpc: Add iommu domain pointer to device archdata Varun Sethi
2013-07-15 4:50 ` [PATCH 2/3 v19] iommu/fsl: Add additional iommu attributes required by the PAMU driver Varun Sethi
2013-07-15 4:50 ` [PATCH 3/3 v18] iommu/fsl: Freescale PAMU driver and iommu implementation Varun Sethi
2013-07-29 12:14 ` Sethi Varun-B16395
2013-08-14 9:48 ` Joerg Roedel [this message]
2013-08-14 9:56 ` [PATCH 1/3] powerpc: Add iommu domain pointer to device archdata Sethi Varun-B16395
2013-08-14 16:15 ` Joerg Roedel
2013-08-14 16:44 ` Sethi Varun-B16395
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=20130814094802.GC4491@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).