linux-kernel - Re: use the generic dma-noncoherent code for microblaze

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: <434e2ef1-3e3f-46d5-a7d1-62ed0e217da0@xilinx.com>
Date:   Fri, 20 Jul 2018 14:33:44 +0200
From:   Michal Simek <michal.simek@...inx.com>
To:     Christoph Hellwig <hch@....de>, Michal Simek <monstr@...str.eu>
CC:     <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org>
Subject: Re: use the generic dma-noncoherent code for microblaze

Hi,

On 19.7.2018 14:54, Christoph Hellwig wrote:
> Hi Michal,
> 
> can you review these patches to switch microblaze to use the generic
> dma-noncoherent code?  All the requirements are in mainline already
> and we've switched various architectures over to it already.
> 

I can't see any issue with them.
Both applied to next.

Thanks,
Michal