From: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.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: "Muszynski, Damian" <damian.muszynski@intel.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
Subject: RE: linux-next: Fixes tag needs some work in the crypto tree
Date: Mon, 19 Sep 2022 09:38:44 +0000 [thread overview]
Message-ID: <CY5PR11MB6366B542EEDCEFCC97F00D2C824D9@CY5PR11MB6366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220919081259.714b81f8@canb.auug.org.au>
My bad. Apologies.
@Herbert, can this be replaced in your history? The correct tag is
Fixes: d370cec32194 ("crypto: qat - Intel(R) QAT crypto interface")
Thanks,
--
Giovanni
-----Original Message-----
From: Stephen Rothwell <sfr@canb.auug.org.au>
Sent: Sunday, September 18, 2022 11:13 PM
To: Herbert Xu <herbert@gondor.apana.org.au>; Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Muszynski, Damian <damian.muszynski@intel.com>; Cabiddu, Giovanni <giovanni.cabiddu@intel.com>; 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
Hi all,
In commit
cf5bb835b7c8 ("crypto: qat - fix DMA transfer direction")
Fixes tag
Fixes: d370cec ("crypto: qat - Intel(R) QAT crypto interface")
has these problem(s):
- SHA1 should be at least 12 digits long
This can be fixed for the future by setting core.abbrev to 12 (or
more) or (for git v2.11 or later) just making sure it is not set
(or set to "auto").
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2022-09-19 9:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 22:12 linux-next: Fixes tag needs some work in the crypto tree Stephen Rothwell
2022-09-19 9:38 ` Cabiddu, Giovanni [this message]
2022-09-20 8:28 ` 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-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-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=CY5PR11MB6366B542EEDCEFCC97F00D2C824D9@CY5PR11MB6366.namprd11.prod.outlook.com \
--to=giovanni.cabiddu@intel.com \
--cc=damian.muszynski@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).