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: <20160621124206.GI28248@8bytes.org>
Date:	Tue, 21 Jun 2016 14:42:07 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Magnus Damm <magnus.damm@...il.com>
Cc:	iommu@...ts.linux-foundation.org,
	laurent.pinchart+renesas@...asonboard.com, geert+renesas@...der.be,
	linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
	horms+renesas@...ge.net.au
Subject: Re: [PATCH v2 00/11] iommu/ipmmu-vmsa: r8a7795 support V2

On Mon, Jun 06, 2016 at 12:57:23PM +0900, Magnus Damm wrote:
>  Developed on top of next-20160602 and:
>  [PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3
> 
>  drivers/iommu/ipmmu-vmsa.c |  318 +++++++++++++++++++++++++++++++++++++-------
>  1 file changed, 269 insertions(+), 49 deletions(-)

Okay, what is the plan on merging this? It is developed on linux-next
and doesn't apply on v4.7-rc4. From the areas it touches it should go
through the iommu-tree, unless there are good reasons not to.


	Joerg

P.S.: Same question applies to your other two patch-sets.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ