From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
thomas.petazzoni@free-electrons.com,
gregory.clement@free-electrons.com,
miquel.raynal@free-electrons.com, oferh@marvell.com,
igall@marvell.com, nadavh@marvell.com,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 0/3] crypto: inside-secure - set of fixes
Date: Mon, 11 Dec 2017 11:51:04 +0100 [thread overview]
Message-ID: <20171211105104.GA25758@kwain> (raw)
In-Reply-To: <20171211084808.8272-1-antoine.tenart@free-electrons.com>
Hi,
I'll send a v4 soon as there are two coding style issues in the series.
I'll also include a new patch to only update the areq->result buffer on
final operations (this will fix the issue I was trying to fix with "only
update the result buffer when provided").
Sorry for the noise.
Antoine
On Mon, Dec 11, 2017 at 09:48:05AM +0100, Antoine Tenart wrote:
> Hi Herbert,
>
> This series is a set of 4 fixes on the Inside Secure SafeXcel crypto
> engine driver. The series will be followed by another non-fix one.
>
> This is based on v4.15-rc3.
>
> Thanks,
> Antoine
>
> Since v2:
> - Removed the patch only update the result buffer when provided.
>
> Since v1:
> - Removed the crash.txt file which was part of patch 1/4.
>
> Antoine Tenart (2):
> crypto: inside-secure - free requests even if their handling failed
> crypto: inside-secure - fix request allocations in invalidation path
>
> Ofer Heifetz (1):
> crypto: inside-secure - per request invalidation
>
> drivers/crypto/inside-secure/safexcel.c | 1 +
> drivers/crypto/inside-secure/safexcel_cipher.c | 83 ++++++++++++++++++++------
> drivers/crypto/inside-secure/safexcel_hash.c | 80 ++++++++++++++++++-------
> 3 files changed, 125 insertions(+), 39 deletions(-)
>
> --
> 2.14.3
>
--
Antoine Ténart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-11 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:48 [PATCH v3 0/3] crypto: inside-secure - set of fixes Antoine Tenart
2017-12-11 8:48 ` [PATCH v3 1/3] crypto: inside-secure - per request invalidation Antoine Tenart
2017-12-11 8:48 ` [PATCH v3 2/3] crypto: inside-secure - free requests even if their handling failed Antoine Tenart
2017-12-11 8:48 ` [PATCH v3 3/3] crypto: inside-secure - fix request allocations in invalidation path Antoine Tenart
2017-12-11 10:51 ` Antoine Tenart [this message]
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=20171211105104.GA25758@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=davem@davemloft.net \
--cc=gregory.clement@free-electrons.com \
--cc=herbert@gondor.apana.org.au \
--cc=igall@marvell.com \
--cc=linux-crypto@vger.kernel.org \
--cc=miquel.raynal@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=oferh@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).