[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CZXXRA9PVPXI.2X41IISN77CUV@kernel.org>
Date: Tue, 19 Mar 2024 20:25:04 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Jarkko Sakkinen" <jarkko@...nel.org>, "Stefan Berger"
<stefanb@...ux.ibm.com>, "Lukas Wunner" <lukas@...ner.de>, "Stefan Berger"
<stefanb@...ux.vnet.ibm.com>
Cc: <keyrings@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
<herbert@...dor.apana.org.au>, <davem@...emloft.net>,
<linux-kernel@...r.kernel.org>, <saulo.alessandre@....jus.br>,
<bbhushan2@...vell.com>
Subject: Re: [PATCH v6 00/13] Add support for NIST P521 to ecdsa
On Tue Mar 19, 2024 at 8:22 PM EET, Jarkko Sakkinen wrote:
> On Tue Mar 19, 2024 at 12:42 AM EET, Stefan Berger wrote:
> >
> >
> > On 3/18/24 14:48, Lukas Wunner wrote:
> > > On Tue, Mar 12, 2024 at 02:36:05PM -0400, Stefan Berger wrote:
> > >> This series adds support for the NIST P521 curve to the ecdsa module
> > >> to enable signature verification with it.
> > >
> > > v6 of this series is still
> > >
> > > Tested-by: Lukas Wunner <lukas@...ner.de>
> >
> > Thanks.
>
> This has been discussed before in LKML but generally tested-by for
> series does not have semantical meaning.
>
> Please apply only for patches that were tested.
How to implement this in practice or place tested-by correctly?
I'd place the tested-by to the patch which contains the uapi trigger
to which for testing was done.
By having this granularity that also does help fixing bugs later on
so it is really not just "plain bureacracy".
BR, Jarkko
Powered by blists - more mailing lists