All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Stephan Mueller <smueller@chronox.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the crypto tree
Date: Mon, 19 Jul 2021 08:13:20 +1000	[thread overview]
Message-ID: <20210719081320.1d205c98@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

Hi all,

In commit

  5261cdf457ce ("crypto: drbg - select SHA512")

Fixes tag

  Fixes: 9b7b94683a9b "crypto: DRBG - switch to HMAC SHA512 DRBG as default

has these problem(s):

  - Subject has leading but no trailing quotes

Please do not split Fixes tags over more than one line.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-07-18 22:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 22:13 Stephen Rothwell [this message]
2021-07-19  5:43 ` linux-next: Fixes tag needs some work in the crypto tree Stephan Mueller
2021-07-19  5:46   ` 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-04-11 22:28 Stephen Rothwell
2019-12-11 20:37 Stephen Rothwell
2019-11-15 23:19 Stephen Rothwell
2019-11-18  7:58 ` Pascal Van Leeuwen
2019-11-18  8:12   ` Stephen Rothwell
2019-11-18 13:04     ` Herbert Xu
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=20210719081320.1d205c98@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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=smueller@chronox.de \
    /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.