All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
	aou@eecs.berkeley.edu, herbert@gondor.apana.org.au,
	davem@davemloft.net, conor.dooley@microchip.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, christoph.muellner@vrull.eu
Subject: Re: [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Date: Thu, 27 Apr 2023 01:28:47 +0200	[thread overview]
Message-ID: <5008634.irdbgypaU6@diego> (raw)
In-Reply-To: <20230426232331.GB65659@sol.localdomain>

Hi,

Am Donnerstag, 27. April 2023, 01:23:31 CEST schrieb Eric Biggers:
> On Thu, Apr 27, 2023 at 01:20:31AM +0200, Heiko Stübner wrote:
> > But for me, this small bit of scalar crypto is also sort of a stepping
> > stone :-). Previous versions [0] already included patches using the
> > vector crypto extensions too, I just split that into a separate thing,
> > as _this_ series actually uses ratified extensions :-)
> > 
> > 
> > Heiko
> > 
> > 
> > 
> > [0] https://lore.kernel.org/lkml/20230313191302.580787-12-heiko.stuebner@vrull.eu/T/
> 
> That patchset wasn't sent to linux-crypto.  Can you make sure to include
> linux-crypto@vger.kernel.org on any subsequent patchsets?  Thanks!

yeah, that was a fault on my part, which I managed to rectify with v4 here
[haven't had time to send the vector part as separate v4 yet]

Will include linux-crypto in further submissions.


Heiko



WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
	aou@eecs.berkeley.edu, herbert@gondor.apana.org.au,
	davem@davemloft.net, conor.dooley@microchip.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, christoph.muellner@vrull.eu
Subject: Re: [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Date: Thu, 27 Apr 2023 01:28:47 +0200	[thread overview]
Message-ID: <5008634.irdbgypaU6@diego> (raw)
In-Reply-To: <20230426232331.GB65659@sol.localdomain>

Hi,

Am Donnerstag, 27. April 2023, 01:23:31 CEST schrieb Eric Biggers:
> On Thu, Apr 27, 2023 at 01:20:31AM +0200, Heiko Stübner wrote:
> > But for me, this small bit of scalar crypto is also sort of a stepping
> > stone :-). Previous versions [0] already included patches using the
> > vector crypto extensions too, I just split that into a separate thing,
> > as _this_ series actually uses ratified extensions :-)
> > 
> > 
> > Heiko
> > 
> > 
> > 
> > [0] https://lore.kernel.org/lkml/20230313191302.580787-12-heiko.stuebner@vrull.eu/T/
> 
> That patchset wasn't sent to linux-crypto.  Can you make sure to include
> linux-crypto@vger.kernel.org on any subsequent patchsets?  Thanks!

yeah, that was a fault on my part, which I managed to rectify with v4 here
[haven't had time to send the vector part as separate v4 yet]

Will include linux-crypto in further submissions.


Heiko



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-04-26 23:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 14:06 [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 1/4] RISC-V: add Zbc extension detection Heiko Stuebner
2023-03-29 14:06   ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 2/4] RISC-V: add Zbkb " Heiko Stuebner
2023-03-29 14:06   ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 3/4] RISC-V: hook new crypto subdir into build-system Heiko Stuebner
2023-03-29 14:06   ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 4/4] RISC-V: crypto: add accelerated GCM GHASH implementation Heiko Stuebner
2023-03-29 14:06   ` Heiko Stuebner
2023-03-29 18:37   ` Eric Biggers
2023-03-29 18:37     ` Eric Biggers
2023-03-29 19:20     ` Heiko Stübner
2023-03-29 19:20       ` Heiko Stübner
2023-04-05 15:04       ` Heiko Stübner
2023-04-05 15:04         ` Heiko Stübner
2023-06-12 14:45         ` Heiko Stübner
2023-06-12 14:45           ` Heiko Stübner
2023-04-11 15:00   ` Nathan Huckleberry
2023-04-11 15:00     ` Nathan Huckleberry
2023-05-11 10:30     ` Heiko Stübner
2023-05-11 10:30       ` Heiko Stübner
2023-05-11 19:02       ` Nathan Huckleberry
2023-05-11 19:02         ` Nathan Huckleberry
2023-03-29 18:43 ` [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions Eric Biggers
2023-03-29 18:43   ` Eric Biggers
2023-04-26 22:55 ` Eric Biggers
2023-04-26 22:55   ` Eric Biggers
2023-04-26 23:20   ` Heiko Stübner
2023-04-26 23:20     ` Heiko Stübner
2023-04-26 23:23     ` Eric Biggers
2023-04-26 23:23       ` Eric Biggers
2023-04-26 23:28       ` Heiko Stübner [this message]
2023-04-26 23:28         ` Heiko Stübner

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=5008634.irdbgypaU6@diego \
    --to=heiko@sntech.de \
    --cc=aou@eecs.berkeley.edu \
    --cc=christoph.muellner@vrull.eu \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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.