linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Thara Gopinath <thara.gopinath@linaro.org>
Cc: davem@davemloft.net, bjorn.andersson@linaro.org,
	ebiggers@google.com, ardb@kernel.org, sivaprak@codeaurora.org,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [Patch v4 0/7] Add support for AEAD algorithms in Qualcomm Crypto Engine driver
Date: Thu, 6 May 2021 06:58:40 +0800	[thread overview]
Message-ID: <20210505225839.uy6zlj3gtp77uuqk@gondor.apana.org.au> (raw)
In-Reply-To: <48d51bb5-a107-4756-4767-f62131d28505@linaro.org>

On Wed, May 05, 2021 at 06:54:18PM -0400, Thara Gopinath wrote:
> 
> 
> On 4/29/21 11:07 AM, Thara Gopinath wrote:
> > Enable support for AEAD algorithms in Qualcomm CE driver.  The first three
> > patches in this series are cleanups and add a few missing pieces required
> > to add support for AEAD algorithms.  Patch 4 introduces supported AEAD
> > transformations on Qualcomm CE.  Patches 5 and 6 implements the h/w
> > infrastructure needed to enable and run the AEAD transformations on
> > Qualcomm CE.  Patch 7 adds support to queue fallback algorithms in case of
> > unsupported special inputs.
> > 
> > This patch series has been tested with in kernel crypto testing module
> > tcrypt.ko with fuzz tests enabled as well.
> 
> Hi Herbert,
> 
> I have fixed all the review comments on this series and fuzz tests pass as
> well. Do you think this can be merged ?

We're still in the merge window, no new features are accepted
at this point.  Please be patient.

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

  reply	other threads:[~2021-05-05 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 15:07 [Patch v4 0/7] Add support for AEAD algorithms in Qualcomm Crypto Engine driver Thara Gopinath
2021-04-29 15:07 ` [Patch v4 1/7] crypto: qce: common: Add MAC failed error checking Thara Gopinath
2021-04-29 15:07 ` [Patch v4 2/7] crypto: qce: common: Make result dump optional Thara Gopinath
2021-04-29 15:07 ` [Patch v4 3/7] crypto: qce: Add mode for rfc4309 Thara Gopinath
2021-04-29 15:07 ` [Patch v4 4/7] crypto: qce: Add support for AEAD algorithms Thara Gopinath
2021-04-29 15:07 ` [Patch v4 5/7] crypto: qce: common: Clean up qce_auth_cfg Thara Gopinath
2021-04-29 15:07 ` [Patch v4 6/7] crypto: qce: common: Add support for AEAD algorithms Thara Gopinath
2021-04-29 15:07 ` [Patch v4 7/7] crypto: qce: aead: Schedule fallback algorithm Thara Gopinath
2021-05-05 22:54 ` [Patch v4 0/7] Add support for AEAD algorithms in Qualcomm Crypto Engine driver Thara Gopinath
2021-05-05 22:58   ` Herbert Xu [this message]
2021-05-05 23:00     ` Thara Gopinath
2021-05-14 11:35 ` 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=20210505225839.uy6zlj3gtp77uuqk@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=ardb@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sivaprak@codeaurora.org \
    --cc=thara.gopinath@linaro.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).