All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: Fixes tag needs some work in the crypto tree
Date: Mon, 18 Nov 2019 07:58:42 +0000	[thread overview]
Message-ID: <MN2PR20MB2973E1EAD50B58826FCEC763CA4D0@MN2PR20MB2973.namprd20.prod.outlook.com> (raw)
In-Reply-To: <20191116101954.33672f2d@canb.auug.org.au>

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

  reply	other threads:[~2019-11-18  7:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 23:19 linux-next: Fixes tag needs some work in the crypto tree Stephen Rothwell
2019-11-18  7:58 ` Pascal Van Leeuwen [this message]
2019-11-18  8:12   ` Stephen Rothwell
2019-11-18 13:04     ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2023-10-02 21:03 Stephen Rothwell
2023-07-23 22:37 Stephen Rothwell
2023-07-24  1:54 ` Weili Qian
2022-09-18 22:12 Stephen Rothwell
2022-09-19  9:38 ` Cabiddu, Giovanni
2022-09-20  8:28   ` Herbert Xu
2022-04-18 21:17 Stephen Rothwell
2022-04-19 10:41 ` Giovanni Cabiddu
2021-07-18 22:13 Stephen Rothwell
2021-07-19  5:43 ` Stephan Mueller
2021-07-19  5:46   ` Herbert Xu
2021-04-11 22:28 Stephen Rothwell
2019-12-11 20:37 Stephen Rothwell
2019-08-02  6:02 Stephen Rothwell
2019-04-22 21:30 Stephen Rothwell
2019-04-23  4:08 ` Herbert Xu
2019-04-15 21:23 Stephen Rothwell
2019-04-16  1:05 ` Herbert Xu

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=MN2PR20MB2973E1EAD50B58826FCEC763CA4D0@MN2PR20MB2973.namprd20.prod.outlook.com \
    --to=pvanleeuwen@verimatrix.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.