From: Eric Biggers <ebiggers@kernel.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linus.walleij@linaro.org, linux@armlinux.org.uk,
robh+dt@kernel.org, ulli.kroll@googlemail.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] crypto: add gemini/sl3516 crypto driver
Date: Wed, 19 May 2021 11:39:23 -0700 [thread overview]
Message-ID: <YKVbW8T92bY3NG4u@gmail.com> (raw)
In-Reply-To: <20210518151655.125153-1-clabbe@baylibre.com>
On Tue, May 18, 2021 at 03:16:50PM +0000, Corentin Labbe wrote:
> The gemini SL3516 SoC has a crypto IP.
> This serie had support for it.
>
Please describe how this was tested.
- Eric
_______________________________________________
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:[~2021-05-19 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 15:16 [PATCH 0/5] crypto: add gemini/sl3516 crypto driver Corentin Labbe
2021-05-18 15:16 ` [PATCH 1/5] db-dinding: crypto: Add DT bindings documentation for sl3516-ce Corentin Labbe
2021-05-18 21:38 ` Linus Walleij
2021-05-20 0:04 ` Rob Herring
2021-05-18 15:16 ` [PATCH 2/5] crypto: Add sl3516 crypto engine Corentin Labbe
2021-05-18 21:42 ` Linus Walleij
2021-05-28 7:05 ` Herbert Xu
2021-05-18 15:16 ` [PATCH 3/5] ARM: dts: gemini: add crypto node Corentin Labbe
2021-05-18 21:43 ` Linus Walleij
2021-05-18 15:16 ` [PATCH 4/5] ARM: gemini_config: enable sl3516-ce crypto Corentin Labbe
2021-05-18 21:44 ` Linus Walleij
2021-05-18 15:16 ` [PATCH 5/5] MAINTAINERS: add gemini crypto sl3516-ce Corentin Labbe
2021-05-18 21:45 ` Linus Walleij
2021-05-19 18:39 ` Eric Biggers [this message]
2021-05-20 11:39 ` [PATCH 0/5] crypto: add gemini/sl3516 crypto driver LABBE Corentin
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=YKVbW8T92bY3NG4u@gmail.com \
--to=ebiggers@kernel.org \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=ulli.kroll@googlemail.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).