From: Eric Biggers <ebiggers@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, j-keerthy@ti.com
Subject: Re: [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs
Date: Mon, 15 Jun 2020 11:20:29 -0700 [thread overview]
Message-ID: <20200615182029.GA85413@gmail.com> (raw)
In-Reply-To: <20200615071452.25141-1-t-kristo@ti.com>
On Mon, Jun 15, 2020 at 10:14:45AM +0300, Tero Kristo wrote:
> Hi,
>
> This is basically just a rebase of v2 to 5.8-rc1, and application of
> Rob's Ack on the dt-binding patch. No other changes.
>
> Only driver side + DT binding should be applied via the crypto tree, DTS
> patches should be queued separately via ARM SoC tree (I can take care of
> that myself assuming the driver side gets applied.)
>
> -Tero
Does this driver pass all the crypto self-tests, including with
CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y?
Please include details about testing in your commits.
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-crypto@vger.kernel.org, j-keerthy@ti.com,
herbert@gondor.apana.org.au,
linux-arm-kernel@lists.infradead.org, davem@davemloft.net
Subject: Re: [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs
Date: Mon, 15 Jun 2020 11:20:29 -0700 [thread overview]
Message-ID: <20200615182029.GA85413@gmail.com> (raw)
In-Reply-To: <20200615071452.25141-1-t-kristo@ti.com>
On Mon, Jun 15, 2020 at 10:14:45AM +0300, Tero Kristo wrote:
> Hi,
>
> This is basically just a rebase of v2 to 5.8-rc1, and application of
> Rob's Ack on the dt-binding patch. No other changes.
>
> Only driver side + DT binding should be applied via the crypto tree, DTS
> patches should be queued separately via ARM SoC tree (I can take care of
> that myself assuming the driver side gets applied.)
>
> -Tero
Does this driver pass all the crypto self-tests, including with
CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y?
Please include details about testing in your commits.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-15 18:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 7:14 [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 2/7] crypto: sa2ul: Add crypto driver Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 3/7] crypto: sa2ul: add sha1/sha256/sha512 support Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-26 4:31 ` Herbert Xu
2020-06-26 4:31 ` Herbert Xu
2020-06-26 9:15 ` Tero Kristo
2020-06-26 9:15 ` Tero Kristo
2020-06-30 4:49 ` Herbert Xu
2020-06-30 4:49 ` Herbert Xu
2020-06-30 7:20 ` Tero Kristo
2020-06-30 7:20 ` Tero Kristo
2020-06-30 7:46 ` Herbert Xu
2020-06-30 7:46 ` Herbert Xu
2020-06-30 7:52 ` Tero Kristo
2020-06-30 7:52 ` Tero Kristo
2020-06-30 7:54 ` Herbert Xu
2020-06-30 7:54 ` Herbert Xu
2020-06-30 7:58 ` Tero Kristo
2020-06-30 7:58 ` Tero Kristo
2020-06-30 7:59 ` Herbert Xu
2020-06-30 7:59 ` Herbert Xu
2020-06-30 8:17 ` Tero Kristo
2020-06-30 8:17 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 4/7] crypto: sa2ul: Add AEAD algorithm support Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 5/7] crypto: sa2ul: add device links to child devices Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 6/7] arm64: dts: ti: k3-am6: Add crypto accelarator node Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 7:14 ` [PATCHv4 7/7] arm64: dts: ti: k3-j721e-main: Add crypto accelerator node Tero Kristo
2020-06-15 7:14 ` Tero Kristo
2020-06-15 18:20 ` Eric Biggers [this message]
2020-06-15 18:20 ` [PATCHv4 0/7] crypto: sa2ul support for TI K3 SoCs Eric Biggers
2020-06-16 4:24 ` Tero Kristo
2020-06-16 4:24 ` Tero Kristo
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=20200615182029.GA85413@gmail.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@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 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.