From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tero Kristo <t-kristo@ti.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [RESEND PATCHv3 0/7] crypto: omap: various fixes
Date: Thu, 4 Jun 2020 22:17:39 +1000 [thread overview]
Message-ID: <20200604121739.GA24286@gondor.apana.org.au> (raw)
In-Reply-To: <20200527122429.14888-1-t-kristo@ti.com>
On Wed, May 27, 2020 at 03:24:22PM +0300, Tero Kristo wrote:
> Hi,
>
> Resent the whole series as-per request. Only patch changed compared to
> v2 [1] is patch #3. Cache flushing logic has been fixed on it based on
> comments.
>
> -Tero
>
> [1] https://patchwork.kernel.org/cover/11540265/
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
prev parent reply other threads:[~2020-06-04 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 12:24 [RESEND PATCHv3 0/7] crypto: omap: various fixes Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 1/7] crypto: omap-aes: avoid spamming console with self tests Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 2/7] crypto: omap-sham: force kernel driver usage for sha algos Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 3/7] crypto: omap-crypto: fix userspace copied buffer access Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 4/7] crypto: omap-sham: huge buffer access fixes Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 5/7] crypto: omap-sham: fix very small data size handling Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 6/7] crypto: omap-aes: prevent unregistering algorithms twice Tero Kristo
2020-05-27 12:24 ` [RESEND PATCHv3 7/7] crypto: omap-sham: add proper load balancing support for multicore Tero Kristo
2020-06-04 12:17 ` Herbert Xu [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=20200604121739.GA24286@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@ti.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).