linux-kernel - Re: [PATCH 04/28] Remove EXYNOS_DEV

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: <1397554396.1985.31.camel@x220>
Date:	Tue, 15 Apr 2014 11:33:16 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Sachin Kamat <sachin.kamat@...aro.org>,
	Olof Johansson <olof@...om.net>
Cc:	Richard Weinberger <richard@....at>,
	Joerg Roedel <joro@...tes.org>,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH 04/28] Remove EXYNOS_DEV_SYSMMU

On Mon, 2014-02-10 at 10:02 +0530, Sachin Kamat wrote:
> +cc linux-samsung-soc list
> 
> On 10 February 2014 01:38, Paul Bolle <pebolle@...cali.nl> wrote:
> > I noted this one about a year ago (see
> > https://lkml.org/lkml/2013/3/5/401 ). By now I wonder whether
> > EXYNOS_IOMMU (and everything depending on it) shouldn't be removed. That
> > code has been unbuildable for at least a year now  (I have not checked
> > how much code is involved).
> 
> 
> Please refer to some on-going discussion about it at [1].
> 
> [1] http://thread.gmane.org/gmane.linux.kernel.samsung-soc/26842

It's not clear to me whether an actual decision was eventually made.
Olof, does it make sense to rebase the patch (that Sachin linked to) on
onto v3.15-rc1 and resubmit?


Paul Bolle

--
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/