From: Hiroshi Doyu <hdoyu@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: KyongHo Cho <pullip.cho@samsung.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
<thierry.reding@avionic-design.de>
Subject: Re: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver
Date: Mon, 21 Nov 2011 07:31:01 +0200 [thread overview]
Message-ID: <20111121073101.6b369421.hdoyu@nvidia.com> (raw)
In-Reply-To: <20111118104354.GA19737@8bytes.org>
Hi Joerg,
On Fri, 18 Nov 2011 11:43:54 +0100
Joerg Roedel <joro@8bytes.org> wrote:
> On Fri, Nov 18, 2011 at 07:19:53PM +0900, KyongHo Cho wrote:
>
> > I found that those patches are not IOMMU API implementations.
> > I wonder why they need to be located in drivers/iommu?
>
> The current effort goes into creating a generic framework for IOMMUs.
> These patches create their own framework which is totally the wrong
> direction, they even implement their own version of an IOMMU-API.
>
> I object against merging them until they are converted to the generic
> IOMMU-API.
Ok, I'll in v2 of this patchset.
That was a plan, mentioned in the cover letter of this patchset.
prev parent reply other threads:[~2011-11-21 5:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 11:01 hdoyu
2011-11-17 11:01 ` [PATCH 1/3] ARM: iommu: tegra/common: Initial support for IOVMM driver hdoyu
2011-11-17 20:32 ` Thierry Reding
2011-11-21 8:11 ` Hiroshi Doyu
2011-11-17 11:01 ` [PATCH 2/3] ARM: iommu: tegra2: Initial support for GART driver hdoyu
2011-11-18 7:27 ` Thierry Reding
2011-11-17 11:01 ` [PATCH 3/3] ARM: iommu: tegra3: Initial support for SMMU driver hdoyu
2011-11-18 10:19 ` [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver KyongHo Cho
2011-11-18 10:43 ` Joerg Roedel
2011-11-21 5:31 ` Hiroshi Doyu [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=20111121073101.6b369421.hdoyu@nvidia.com \
--to=hdoyu@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pullip.cho@samsung.com \
--cc=thierry.reding@avionic-design.de \
/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
all inboxes | Powered by JetHome®