From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kevin Hilman <khilman@baylibre•com>, Carlo Caione <carlo@caione•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Christian Hewitt <christianshewitt@gmail•com>
Subject: linux-next: Fixes tags need some work in the amlogic tree
Date: Fri, 4 Oct 2019 06:41:20 +1000 [thread overview]
Message-ID: <20191004064120.6262d85a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi all,
In commit
cb8411a2b051 ("arm64: dts: meson-gxm-khadas-vim2: fix uart_A bluetooth node")
Fixes tag
Fixes: 33344e2111a ("arm64: dts: meson-gxm-khadas-vim2: fix Bluetooth support")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
495637be0e28 ("arm64: dts: meson-gxl-s905x-khadas-vim: fix uart_A bluetooth node")
Fixes tag
Fixes: dd5297cc8b8 ("arm64: dts: meson-gxl-s905x-khadas-vim enable Bluetooth")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
880913b3ccaa ("arm64: dts: meson-gxl-s905x-khadas-vim: fix gpio-keys-polled node")
Fixes tag
Fixes: e15d2774b8c ("ARM64: dts: meson-gxl: add support for the Khadas VIM board")
has these problem(s):
- SHA1 should be at least 12 digits long
These 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 --]
reply other threads:[~2019-10-03 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191004064120.6262d85a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=carlo@caione$(echo .)org \
--cc=christianshewitt@gmail$(echo .)com \
--cc=khilman@baylibre$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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