From: Herbert Xu <herbert@gondor.apana.org.au>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: chohnstaedt@innominate.com, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] crypto: start to fix ixp4xx
Date: Fri, 14 May 2021 19:35:48 +0800 [thread overview]
Message-ID: <20210514113548.bd6lslfjyqxkwyiy@gondor.apana.org.au> (raw)
In-Reply-To: <20210505202618.2663889-1-clabbe@baylibre.com>
On Wed, May 05, 2021 at 08:26:07PM +0000, Corentin Labbe wrote:
> Hello
>
> Loading the ixp4xx crypto driver exhibits lots of error.
> All algorithm fail selftests with different reasons.
> This series start to fixes some of thoses problem.
>
> Corentin Labbe (11):
> crypto: ixp4xx: dma_unmap the correct address
> crypto: ixp4xx: update IV after requests
> crypto: ixp4xx: fallback when having more than one SG
> crypto: ixp4xx: convert unsigned to unsigned int
> crypto: ixp4xx: convert all printk to dev_xxx
> crypto: ixp4xx: whitespace fixes
> crypto: ixp4xx: Do not initialize static to NULL
> crypto: ixp4xx: remove brackets from single statement
> crypto: ixp4xx: Correct functions alignment
> MAINTAINERS: add ixp4xx_crypto to the right arch list
> MAINTAINERS: add myself as maintainer of ixp4xx_crypto
>
> MAINTAINERS | 7 +
> drivers/crypto/Kconfig | 5 +
> drivers/crypto/ixp4xx_crypto.c | 277 +++++++++++++++++++++------------
> 3 files changed, 188 insertions(+), 101 deletions(-)
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2021-05-14 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 20:26 [PATCH 00/11] crypto: start to fix ixp4xx Corentin Labbe
2021-05-05 20:26 ` [PATCH 01/11] crypto: ixp4xx: dma_unmap the correct address Corentin Labbe
2021-05-05 20:26 ` [PATCH 02/11] crypto: ixp4xx: update IV after requests Corentin Labbe
2021-05-05 20:26 ` [PATCH 03/11] crypto: ixp4xx: fallback when having more than one SG Corentin Labbe
2021-05-05 20:26 ` [PATCH 04/11] crypto: ixp4xx: convert unsigned to unsigned int Corentin Labbe
2021-05-05 20:26 ` [PATCH 05/11] crypto: ixp4xx: convert all printk to dev_xxx Corentin Labbe
2021-05-05 20:26 ` [PATCH 06/11] crypto: ixp4xx: whitespace fixes Corentin Labbe
2021-05-05 20:26 ` [PATCH 07/11] crypto: ixp4xx: Do not initialize static to NULL Corentin Labbe
2021-05-05 20:26 ` [PATCH 08/11] crypto: ixp4xx: remove brackets from single statement Corentin Labbe
2021-05-05 20:26 ` [PATCH 09/11] crypto: ixp4xx: Correct functions alignment Corentin Labbe
2021-05-05 20:26 ` [PATCH 10/11] MAINTAINERS: add ixp4xx_crypto to the right arch list Corentin Labbe
2021-05-05 20:26 ` [PATCH 11/11] MAINTAINERS: add myself as maintainer of ixp4xx_crypto Corentin Labbe
2021-05-14 11:35 ` Herbert Xu [this message]
2021-05-17 23:53 ` [PATCH 00/11] crypto: start to fix ixp4xx Linus Walleij
2021-05-18 1:19 ` Herbert Xu
2021-05-18 21:36 ` Linus Walleij
2021-05-19 0:51 ` 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=20210514113548.bd6lslfjyqxkwyiy@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=chohnstaedt@innominate.com \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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).