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

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: <20180802020906.GK1392@brightrain.aerifal.cx>
Date:   Wed, 1 Aug 2018 22:09:06 -0400
From:   Rich Felker <dalias@...c.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Jacopo Mondi <jacopo+renesas@...ndi.org>,
        Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
        linux-sh@...r.kernel.org, iommu@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: use the generic dma-noncoherent code for sh V3

On Tue, Jul 31, 2018 at 09:24:13AM +0200, Christoph Hellwig wrote:
> On Tue, Jul 31, 2018 at 03:06:13PM +0900, Yoshinori Sato wrote:
> > On Wed, 25 Jul 2018 18:40:38 +0900,
> > Christoph Hellwig wrote:
> > > 
> > > Hi all,
> > > 
> > > can you review these patches to switch sh to use the generic
> > > dma-noncoherent code?  All the requirements are in mainline already
> > > and we've switched various architectures over to it already.
> > > 
> > > Changes since V2:
> > >  - drop a now obsolete export
> > > 
> > > Changes since V1:
> > >  - fixed two stupid compile errors and verified them using a local
> > >    cross toolchain instead of the 0day buildbot
> > 
> > Acked-by: Yoshinori Sato <ysato@...rs.sourceforge.jp>
> 
> Do you want to pull this in through the sh tree?  If not I'd be happy
> to take it through the dma mapping tree.

Usually I send the pull requests for sh tree, and I'm trying to figure
out which patches are okay to merge and prepare one now, but if you're
happy to take it through the dma mapping tree go ahead, and I'll focus
on other sh stuff that needs attention.

Rich