From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 16 Apr 2019 09:05:48 +0800 [thread overview]
Message-ID: <20190416010548.tnos7ro7rvi6mqqc@gondor.apana.org.au> (raw)
In-Reply-To: <20190416072342.739863fb@canb.auug.org.au>
On Tue, Apr 16, 2019 at 07:23:42AM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> In commit
>
> 2e53582d158e ("crypto: mxc-scc - Remove broken driver")
>
> Fixes tag
>
> Fixes: d293b640ebd ("crypto: mxc-scc - add basic driver for the...")
>
> 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").
Thanks Stephen, it should be fixed now.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2019-04-16 1:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 21:23 linux-next: Fixes tag needs some work in the crypto tree Stephen Rothwell
2019-04-16 1:05 ` Herbert Xu [this message]
2019-04-22 21:30 Stephen Rothwell
2019-04-23 4:08 ` Herbert Xu
2019-08-02 6:02 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-12-11 20:37 Stephen Rothwell
2021-04-11 22:28 Stephen Rothwell
2021-07-18 22:13 Stephen Rothwell
2021-07-19 5:43 ` Stephan Mueller
2021-07-19 5:46 ` Herbert Xu
2022-04-18 21:17 Stephen Rothwell
2022-04-19 10:41 ` Giovanni Cabiddu
2022-09-18 22:12 Stephen Rothwell
2022-09-19 9:38 ` Cabiddu, Giovanni
2022-09-20 8:28 ` Herbert Xu
2023-07-23 22:37 Stephen Rothwell
2023-07-24 1:54 ` Weili Qian
2023-10-02 21:03 Stephen Rothwell
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=20190416010548.tnos7ro7rvi6mqqc@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--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).