From: Eric Biggers <ebiggers@kernel.org>
To: Sebastien Buisson <sbuisson@ddn.com>
Cc: Sebastien Buisson <sbuisson.ddn@gmail.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] crypto: add adler32 to CryptoAPI
Date: Tue, 2 Jun 2020 09:06:39 -0700 [thread overview]
Message-ID: <20200602160639.GA85856@gmail.com> (raw)
In-Reply-To: <B28A02E7-BE74-4ACE-981F-0CE47AC80CFE@ddn.com>
On Tue, Jun 02, 2020 at 03:59:40PM +0000, Sebastien Buisson wrote:
>
> > Le 1 juin 2020 à 09:13, Eric Biggers <ebiggers@kernel.org> a écrit :
> >
> > On Thu, May 28, 2020 at 07:00:51PM +0200, sbuisson.ddn@gmail.com wrote:
> >> From: Sebastien Buisson <sbuisson@whamcloud.com>
> >>
> >> Add adler32 to CryptoAPI so that it can be used with the normal kernel
> >> API, and potentially accelerated if architecture-specific
> >> optimizations are available.
> >>
> >> Signed-off-by: Sebastien Buisson <sbuisson@whamcloud.com>
> >> ---
> >> crypto/Kconfig | 7 +
> >> crypto/Makefile | 1 +
> >> crypto/adler32_zlib.c | 117 ++++++++++++++++
> >> crypto/testmgr.c | 7 +
> >> crypto/testmgr.h | 362 ++++++++++++++++++++++++++++++++++++++++++++++++++
> >> 5 files changed, 494 insertions(+)
> >> create mode 100644 crypto/adler32_zlib.c
> >
> > Did you actually run the self-tests for this? They fail for me.
>
> I was wondering how to run testmgr tests alone?
Just boot with:
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y
Then check dmesg or /proc/crypto.
- Eric
prev parent reply other threads:[~2020-06-02 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 17:00 [PATCH] crypto: add adler32 to CryptoAPI sbuisson.ddn
2020-05-29 2:20 ` Herbert Xu
2020-06-01 7:13 ` Eric Biggers
2020-06-02 15:59 ` Sebastien Buisson
2020-06-02 16:06 ` Eric Biggers [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=20200602160639.GA85856@gmail.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=sbuisson.ddn@gmail.com \
--cc=sbuisson@ddn.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).