From: Lars Persson <lars.persson@axis.com>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Cc: Lars Persson <larper@axis.com>
Subject: [PATCH 0/7] crypto: axis - fixes for the Artpec SoCs
Date: Wed, 23 Jan 2019 12:59:39 +0100 [thread overview]
Message-ID: <cover.1548243646.git.larper@axis.com> (raw)
Hi
This series brings to mainline fixes done during our product development and
fixes for errors detected by the IPsec testsuite in LTP.
Lars Persson (6):
crypto: axis - remove sha384 support for artpec7
crypto: axis - remove sha512 support for artpec7
crypto: axis - fix for recursive locking from bottom half
crypto: axis - give DMA the start of the status buffer
crypto: axis - support variable AEAD tag length
crypto: axis - use a constant time tag compare
Vincent Whitchurch (1):
crypto: axis - move request unmap outside of the queue lock
drivers/crypto/axis/artpec6_crypto.c | 317 ++++++++---------------------------
1 file changed, 71 insertions(+), 246 deletions(-)
--
2.11.0
next reply other threads:[~2019-01-23 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 11:59 Lars Persson [this message]
2019-01-23 11:59 ` [PATCH 1/7] crypto: axis - remove sha384 support for artpec7 Lars Persson
2019-01-23 11:59 ` [PATCH 2/7] crypto: axis - remove sha512 " Lars Persson
2019-01-23 11:59 ` [PATCH 3/7] crypto: axis - fix for recursive locking from bottom half Lars Persson
2019-01-23 11:59 ` [PATCH 4/7] crypto: axis - give DMA the start of the status buffer Lars Persson
2019-01-23 11:59 ` [PATCH 5/7] crypto: axis - support variable AEAD tag length Lars Persson
2019-01-23 11:59 ` [PATCH 6/7] crypto: axis - use a constant time tag compare Lars Persson
2019-01-23 11:59 ` [PATCH 7/7] crypto: axis - move request unmap outside of the queue lock Lars Persson
2019-02-01 6:49 ` [PATCH 0/7] crypto: axis - fixes for the Artpec SoCs 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=cover.1548243646.git.larper@axis.com \
--to=lars.persson@axis.com \
--cc=herbert@gondor.apana.org.au \
--cc=larper@axis.com \
--cc=linux-crypto@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 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).