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@xxxxxxxxxxxxxxx <linux-crypto-owner@xxxxxxxxxxxxxxx> On Behalf Of
> Stephen Rothwell
> Sent: Saturday, November 16, 2019 12:20 AM
> To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>; Linux Crypto List <linux-crypto@xxxxxxxxxxxxxxx>
> Cc: Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>; Linux Kernel Mailing List <linux-
> kernel@xxxxxxxxxxxxxxx>; Pascal van Leeuwen <pascalvanl@xxxxxxxxx>
> 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
