All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastien Buisson <sbuisson@ddn.com>
To: Eric Biggers <ebiggers@kernel.org>
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>,
	Sebastien Buisson <sbuisson@ddn.com>
Subject: Re: [PATCH] crypto: add adler32 to CryptoAPI
Date: Tue, 2 Jun 2020 15:59:40 +0000	[thread overview]
Message-ID: <B28A02E7-BE74-4ACE-981F-0CE47AC80CFE@ddn.com> (raw)
In-Reply-To: <20200601071320.GE11054@sol.localdomain>


> 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?

  reply	other threads:[~2020-06-02 15:59 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 [this message]
2020-06-02 16:06     ` Eric Biggers

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=B28A02E7-BE74-4ACE-981F-0CE47AC80CFE@ddn.com \
    --to=sbuisson@ddn.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=sbuisson.ddn@gmail.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.