[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CZX83UT326IV.3KOKLZ23UH9EZ@kernel.org>
Date: Tue, 19 Mar 2024 00:19:01 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Lukas Wunner" <lukas@...ner.de>
Cc: "Stefan Berger" <stefanb@...ux.vnet.ibm.com>,
<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>, "Stefan Berger" <stefanb@...ux.ibm.com>
Subject: Re: [PATCH v6 04/13] crypto: ecdsa - Extend res.x mod n calculation
for NIST P521
On Mon Mar 18, 2024 at 10:39 PM EET, Lukas Wunner wrote:
> On Mon, Mar 18, 2024 at 10:33:47PM +0200, Jarkko Sakkinen wrote:
> > On Tue Mar 12, 2024 at 8:36 PM EET, Stefan Berger wrote:
> > > Signed-off-by: Stefan Berger <stefanb@...ux.ibm.com>
> > > Tested-by: Lukas Wunner <lukas@...ner.de>
> >
> > What was there to test in this anyway? I see only comment change below.
>
> The full series was tested, irrespective of the content of the individual
> patches.
Tested-by's should be per patch, and in this patch tested-by has no
meaning at all.
In order to determine which patches tested-by is applicable it can
be derived on what was actually tested.
This looks as tested-by was used in place of acked/reviewed-by, which
is not how it should be used.
BR, Jarkko
Powered by blists - more mailing lists