From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Sverdlin <alexander.sverdlin@nokia.com>
Subject: linux-next: Fixes tag needs some work in the crypto tree
Date: Fri, 2 Aug 2019 16:02:14 +1000 [thread overview]
Message-ID: <20190802160214.171eabe8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
Hi all,
In commit
1b82feb6c5e1 ("crypto: qat - Silence smp_processor_id() warning")
Fixes tag
Fixes: ed8ccaef52 ("crypto: qat - Add support for SRIOV")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-02 6:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 6:02 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 21:03 linux-next: Fixes tag needs some work in the crypto tree 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-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-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=20190802160214.171eabe8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexander.sverdlin@nokia.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).