public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Thorsten Blum <thorsten.blum@linux•dev>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: "David S. Miller" <davem@davemloft•net>,
	Nicolas Ferre <nicolas.ferre@microchip•com>,
	Alexandre Belloni <alexandre.belloni@bootlin•com>,
	Claudiu Beznea <claudiu.beznea@tuxon•dev>,
	linux-crypto@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH 1/2] crypto: atmel-ecc - add support for atecc608b
Date: Sun, 12 Apr 2026 09:18:13 +0200	[thread overview]
Message-ID: <adtHNa-eMUQO0JqX@linux.dev> (raw)
In-Reply-To: <adsyzmm3WSZ1ao4a@gondor.apana.org.au>

On Sun, Apr 12, 2026 at 01:51:10PM +0800, Herbert Xu wrote:
> On Mon, Mar 30, 2026 at 12:08:00PM +0200, Thorsten Blum wrote:
> > Tested on hardware with an ATECC608B at 0x60. The device binds
> > successfully, passes the driver's sanity check, and registers the
> > ecdh-nist-p256 KPP algorithm.
> > 
> > The hardware ECDH path was also exercised using a minimal KPP test
> > module, covering private key generation, public key derivation, and
> > shared secret computation.
> > 
> > Signed-off-by: Thorsten Blum <thorsten.blum@linux•dev>
> > ---
> >  drivers/crypto/atmel-ecc.c | 3 +++
> >  1 file changed, 3 insertions(+)
> 
> Is there supposed to be a 2/2 or should I apply this patch on its
> own?

Patch 2/2 is here:

https://lore.kernel.org/lkml/20260330100800.389042-4-thorsten.blum@linux.dev/

Thanks,
Thorsten


  reply	other threads:[~2026-04-12  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 10:08 [PATCH 1/2] crypto: atmel-ecc - add support for atecc608b Thorsten Blum
2026-04-12  5:51 ` Herbert Xu
2026-04-12  7:18   ` Thorsten Blum [this message]
2026-04-12  8:37     ` 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=adtHNa-eMUQO0JqX@linux.dev \
    --to=thorsten.blum@linux$(echo .)dev \
    --cc=alexandre.belloni@bootlin$(echo .)com \
    --cc=claudiu.beznea@tuxon$(echo .)dev \
    --cc=davem@davemloft$(echo .)net \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=nicolas.ferre@microchip$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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