From: Eric Biggers <ebiggers@kernel.org>
To: Srujana Challa <schalla@marvell.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, pathreya@marvell.com,
schandran@marvell.com, arno@natisbad.org, bbrezillon@kernel.org
Subject: Re: [PATCH v2 0/4] Add Support for Marvell OcteonTX Cryptographic
Date: Thu, 19 Mar 2020 22:31:49 -0700 [thread overview]
Message-ID: <20200320053149.GC1315@sol.localdomain> (raw)
In-Reply-To: <1584100028-21279-1-git-send-email-schalla@marvell.com>
On Fri, Mar 13, 2020 at 05:17:04PM +0530, Srujana Challa wrote:
> The following series adds support for Marvell Cryptographic Accelerarion
> Unit (CPT) on OcteonTX CN83XX SoC.
>
> Changes since v1:
> * Replaced CRYPTO_BLKCIPHER with CRYPTO_SKCIPHER in Kconfig.
>
> Srujana Challa (4):
> drivers: crypto: create common Kconfig and Makefile for Marvell
> drivers: crypto: add support for OCTEON TX CPT engine
> drivers: crypto: add the Virtual Function driver for CPT
> crypto: marvell: enable OcteonTX cpt options for build
There's no mention of testing. Did you try CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y?
- Eric
next prev parent reply other threads:[~2020-03-20 5:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 11:47 [PATCH v2 0/4] Add Support for Marvell OcteonTX Cryptographic Srujana Challa
2020-03-13 11:47 ` [PATCH v2 1/4] drivers: crypto: create common Kconfig and Makefile for Marvell Srujana Challa
2020-03-13 11:47 ` [PATCH v2 2/4] drivers: crypto: add support for OCTEON TX CPT engine Srujana Challa
2020-03-13 11:47 ` [PATCH v2 3/4] drivers: crypto: add the Virtual Function driver for CPT Srujana Challa
2020-03-13 11:47 ` [PATCH v2 4/4] crypto: marvell: enable OcteonTX cpt options for build Srujana Challa
2020-03-20 3:51 ` [PATCH v2 0/4] Add Support for Marvell OcteonTX Cryptographic Herbert Xu
2020-03-20 5:31 ` Eric Biggers [this message]
2020-03-20 10:47 ` [EXT] " Srujana Challa
2020-03-21 12:31 ` Ard Biesheuvel
2020-03-23 3:20 ` Srujana Challa
2020-04-13 13:21 ` Srujana Challa
2020-04-13 13:47 ` Ard Biesheuvel
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=20200320053149.GC1315@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pathreya@marvell.com \
--cc=schalla@marvell.com \
--cc=schandran@marvell.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).