[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN2PR20MB2973E1EAD50B58826FCEC763CA4D0@MN2PR20MB2973.namprd20.prod.outlook.com>
Date: Mon, 18 Nov 2019 07:58:42 +0000
From: Pascal Van Leeuwen <pvanleeuwen@...imatrix.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Herbert Xu <herbert@...dor.apana.org.au>,
Linux Crypto List <linux-crypto@...r.kernel.org>
CC: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: Fixes tag needs some work in the crypto tree
Stephen, Herbert,
My bad, I didn't know the Fixes tag should not be broken over
lines (and that rather conflicted with the 75 characters per
line rule here, which is why I did break it up).
I'm willing to fix that - except that I don't know how to create
a patch that _only_ fixes the commit description of something
already pulled into the cryptodev tree?
Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Verimatrix
www.insidesecure.com
> -----Original Message-----
> From: linux-crypto-owner@...r.kernel.org <linux-crypto-owner@...r.kernel.org> On Behalf Of
> Stephen Rothwell
> Sent: Saturday, November 16, 2019 12:20 AM
> To: Herbert Xu <herbert@...dor.apana.org.au>; Linux Crypto List <linux-crypto@...r.kernel.org>
> Cc: Linux Next Mailing List <linux-next@...r.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@...r.kernel.org>; Pascal van Leeuwen <pascalvanl@...il.com>
> Subject: linux-next: Fixes tag needs some work in the crypto tree
>
> Hi all,
>
> In commit
>
> 8c2c43a5be3d ("crypto: inside-secure - Fixed authenc w/ (3)DES fails on Macchiatobin")
>
> Fixes tag
>
> Fixes: 13a1bb93f7b1c9 ("crypto: inside-secure - Fixed warnings on
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over more than one line.
>
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists