From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: KyongHo Cho <pullip.cho-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver
Date: Fri, 18 Nov 2011 11:43:54 +0100 [thread overview]
Message-ID: <20111118104354.GA19737@8bytes.org> (raw)
In-Reply-To: <CAHQjnOM-N9suPrv_nSRQsxGCNrf77rFLNtRcOdsjyz_O6bGdpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver
Date: Fri, 18 Nov 2011 11:43:54 +0100 [thread overview]
Message-ID: <20111118104354.GA19737@8bytes.org> (raw)
In-Reply-To: <CAHQjnOM-N9suPrv_nSRQsxGCNrf77rFLNtRcOdsjyz_O6bGdpA@mail.gmail.com>
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.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: KyongHo Cho <pullip.cho@samsung.com>
Cc: hdoyu@nvidia.com, linux-tegra@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver
Date: Fri, 18 Nov 2011 11:43:54 +0100 [thread overview]
Message-ID: <20111118104354.GA19737@8bytes.org> (raw)
In-Reply-To: <CAHQjnOM-N9suPrv_nSRQsxGCNrf77rFLNtRcOdsjyz_O6bGdpA@mail.gmail.com>
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.
Joerg
next prev parent reply other threads:[~2011-11-18 10:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 11:01 [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver hdoyu-DDmLM1+adcrQT0dZR+AlfA
2011-11-17 11:01 ` hdoyu
2011-11-17 11:01 ` hdoyu at nvidia.com
[not found] ` <1321527667-12923-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-17 11:01 ` [PATCH 1/3] ARM: iommu: tegra/common: Initial support for IOVMM driver hdoyu-DDmLM1+adcrQT0dZR+AlfA
2011-11-17 11:01 ` hdoyu
2011-11-17 11:01 ` hdoyu at nvidia.com
[not found] ` <1321527667-12923-2-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-17 20:32 ` Thierry Reding
2011-11-17 20:32 ` Thierry Reding
2011-11-17 20:32 ` Thierry Reding
[not found] ` <20111117203202.GB20889-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2011-11-21 8:11 ` Hiroshi Doyu
2011-11-21 8:11 ` Hiroshi Doyu
2011-11-21 8:11 ` Hiroshi Doyu
2011-11-17 11:01 ` [PATCH 2/3] ARM: iommu: tegra2: Initial support for GART driver hdoyu-DDmLM1+adcrQT0dZR+AlfA
2011-11-17 11:01 ` hdoyu
2011-11-17 11:01 ` hdoyu at nvidia.com
[not found] ` <1321527667-12923-3-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-18 7:27 ` Thierry Reding
2011-11-18 7:27 ` Thierry Reding
2011-11-18 7:27 ` Thierry Reding
2011-11-18 10:19 ` [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver KyongHo Cho
2011-11-18 10:19 ` KyongHo Cho
2011-11-18 10:19 ` KyongHo Cho
[not found] ` <CAHQjnOM-N9suPrv_nSRQsxGCNrf77rFLNtRcOdsjyz_O6bGdpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-18 10:43 ` Joerg Roedel [this message]
2011-11-18 10:43 ` Joerg Roedel
2011-11-18 10:43 ` Joerg Roedel
[not found] ` <20111118104354.GA19737-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2011-11-21 5:31 ` Hiroshi Doyu
2011-11-21 5:31 ` Hiroshi Doyu
2011-11-21 5:31 ` Hiroshi Doyu
2011-11-17 11:01 ` [PATCH 3/3] ARM: iommu: tegra3: Initial support for SMMU driver hdoyu
2011-11-17 11:01 ` hdoyu
2011-11-17 11:01 ` hdoyu at nvidia.com
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=20111118104354.GA19737@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pullip.cho-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.