From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tomasz Maciej Nowak <tmn505@gmail.com>
Subject: linux-next: Fixes tags need some work in the mvebu tree
Date: Sat, 14 Mar 2020 21:37:36 +1100 [thread overview]
Message-ID: <20200314213736.2d5822ca@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi all,
n commit
17ac1b98b905 ("arm64: dts: marvell: build ESPRESSObin variants")
Fixes tag
Fixes: 447b878935 ("arm64: dts: marvell: add ESPRESSObin variants")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
bb771464c19a ("arm64: dts: marvell: espressobin: indicate dts version")
Fixes tag
Fixes: 447b878935 ("arm64: dts: marvell: add ESPRESSObin variants")
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:[~2020-03-15 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 10:37 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 20:38 linux-next: Fixes tags need some work in the mvebu tree Stephen Rothwell
2019-10-08 20:50 ` Marek Behun
2019-10-09 7:17 ` Gregory CLEMENT
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=20200314213736.2d5822ca@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tmn505@gmail.com \
/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).