From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/4] crypto: talitos: dma_map_sg can handle chained SG
Date: Mon, 28 Sep 2015 11:43:34 +0200 [thread overview]
Message-ID: <20150928094334.GA15502@Red> (raw)
In-Reply-To: <560295FA.7070005@c-s.fr>
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
next prev parent reply other threads:[~2015-09-28 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 11:55 [PATCH] crypto: dma_map_sg can handle chained SG LABBE Corentin
2015-09-23 11:55 ` [PATCH 1/4] crypto: talitos: " LABBE Corentin
2015-09-23 12:07 ` Christophe Leroy
2015-09-28 9:43 ` LABBE Corentin [this message]
2015-09-23 11:55 ` [PATCH 2/4] crypto: qce: " LABBE Corentin
2015-09-23 19:47 ` Stanimir Varbanov
2015-10-01 13:58 ` Herbert Xu
2015-09-23 11:55 ` [PATCH 3/4] crypto: caam: " LABBE Corentin
2015-09-23 11:55 ` [PATCH 4/4] crypto: sahara: " LABBE Corentin
2015-10-01 14:01 ` [PATCH] crypto: " Herbert Xu
2015-10-02 6:01 ` [PATCH] crypto: qce: " LABBE Corentin
2015-10-08 14:23 ` Herbert Xu
2015-11-03 10:39 ` Stanimir Varbanov
2015-11-03 12:36 ` LABBE Corentin
2015-11-03 13:33 ` Stanimir Varbanov
2015-11-04 5:02 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150928094334.GA15502@Red \
--to=clabbe.montjoie@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.