linux-kernel - Re: [PATCH 1/4] crypto: talitos: dma_map

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]

Date:	Mon, 28 Sep 2015 11:43:34 +0200
From:	LABBE Corentin <clabbe.montjoie@...il.com>
To:	Christophe Leroy <christophe.leroy@....fr>
Cc:	herbert@...dor.apana.org.au, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org
Subject: Re: [PATCH 1/4] crypto: talitos: dma_map_sg can handle chained SG

On Wed, Sep 23, 2015 at 02:07:22PM +0200, Christophe Leroy wrote:
> 
> Le 23/09/2015 13:55, LABBE Corentin a écrit :
> > The talitos driver use two dma_map_sg path
> > according to SG are chained or not.
> > Since dma_map_sg can handle both case, clean the code with all
> > references to sg chained.
> >
> > Thus removing talitos_map_sg, talitos_unmap_sg_chain
> > and sg_count functions.
> >
> >
> Shouldn't the replacement of sg_count()  by sg_nents_for_len() be part 
> of second patch ?
> 

No because I remove also the chained argument of sg_count, so splitting this patch
with a dedicated patch for removing sg_count is not good.

Regards

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