linux-kernel - Re: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111118104354.GA19737@8bytes.org>
Date:	Fri, 18 Nov 2011 11:43:54 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	KyongHo Cho <pullip.cho@...sung.com>
Cc:	hdoyu@...dia.com, linux-tegra@...r.kernel.org,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] ARM: iommu: tegra: Add initial Tegra IOMMU driver

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/