From: Antoine Tenart <antoine.tenart@bootlin.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, maxime.chevallier@bootlin.com,
gregory.clement@bootlin.com, miquel.raynal@bootlin.com,
nadavh@marvell.com, oferh@marvell.com, igall@marvell.com
Subject: [PATCH v2 0/9] crypto: inside-secure - hmac(sha256/sha224) support
Date: Mon, 19 Mar 2018 09:21:12 +0100 [thread overview]
Message-ID: <20180319082121.32103-1-antoine.tenart@bootlin.com> (raw)
Hi Herbert,
This series brings hmac(sha256) and hmac(sha224) support to the Inside
Secure cryptographic engine driver.
The first 7 patches are fixes and reworks needed for the hmac(sha256)
and hmac(224) support to land in. Then 2 patches adds the 2 new
algorithms.
This has been tested with boot tests, tcrypt and IPsec traffic. This
series is a preparation series for more algorithms support (so that
the series are smaller and easier to review).
Thanks,
Antoine
Since v1:
- Fixed a kbuild reported compilation issue.
- Added missing commit messages in the last 2 patches.
- Removed 3 patches from the series that already were applied in
the cryptodev tree.
Antoine Tenart (9):
crypto: inside-secure - move the digest to the request context
crypto: inside-secure - fix typo s/allways/always/ in a define
crypto: inside-secure - fix a typo in a register name
crypto: inside-secure - improve the send error path
crypto: inside-secure - do not access buffers mapped to the device
crypto: inside-secure - improve the skcipher token
crypto: inside-secure - the context ipad/opad should use the state sz
crypto: inside-secure - hmac(sha256) support
crypto: inside-secure - hmac(sha224) support
drivers/crypto/inside-secure/safexcel.c | 8 +-
drivers/crypto/inside-secure/safexcel.h | 6 +-
drivers/crypto/inside-secure/safexcel_cipher.c | 3 +-
drivers/crypto/inside-secure/safexcel_hash.c | 189 +++++++++++++++++++++----
4 files changed, 170 insertions(+), 36 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-19 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 8:21 Antoine Tenart [this message]
2018-03-19 8:21 ` [PATCH v2 1/9] crypto: inside-secure - move the digest to the request context Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 2/9] crypto: inside-secure - fix typo s/allways/always/ in a define Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 3/9] crypto: inside-secure - fix a typo in a register name Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 4/9] crypto: inside-secure - improve the send error path Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 5/9] crypto: inside-secure - do not access buffers mapped to the device Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 6/9] crypto: inside-secure - improve the skcipher token Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 7/9] crypto: inside-secure - the context ipad/opad should use the state sz Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 8/9] crypto: inside-secure - hmac(sha256) support Antoine Tenart
2018-03-19 8:21 ` [PATCH v2 9/9] crypto: inside-secure - hmac(sha224) support Antoine Tenart
2018-03-30 17:40 ` [PATCH v2 0/9] crypto: inside-secure - hmac(sha256/sha224) support 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=20180319082121.32103-1-antoine.tenart@bootlin.com \
--to=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=gregory.clement@bootlin.com \
--cc=herbert@gondor.apana.org.au \
--cc=igall@marvell.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=nadavh@marvell.com \
--cc=oferh@marvell.com \
--cc=thomas.petazzoni@bootlin.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 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.