public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mike Turquette <mturquette@baylibre•com>,
	Stephen Boyd <sboyd@kernel•org>
Cc: Robert Hancock <robert.hancock@calian•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags need some work in the clk tree
Date: Mon, 28 Jun 2021 21:44:30 +1000	[thread overview]
Message-ID: <20210628214430.6b3607d5@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

Hi all,

In commit

  3c9b49b0031a ("clk: si5341: Update initialization magic")

Fixes tag

  Fixes: 3044a860fd ("clk: Add Si5341/Si5340 driver")

has these problem(s):

  - SHA1 should be at least 12 digits long

In commit

  71dcc4d1f7d2 ("clk: si5341: Check for input clock presence and PLL lock on startup")

Fixes tag

  Fixes: 3044a860fd ("clk: Add Si5341/Si5340 driver")

has these problem(s):

  - SHA1 should be at least 12 digits long

In commit

  78f6f406026d ("clk: si5341: Avoid divide errors due to bogus register contents")

Fixes tag

  Fixes: 3044a860fd ("clk: Add Si5341/Si5340 driver")

has these problem(s):

  - SHA1 should be at least 12 digits long

In commit

  6e7d2de1e000 ("clk: si5341: Wait for DEVICE_READY on startup")

Fixes tag

  Fixes: 3044a860fd ("clk: Add Si5341/Si5340 driver")

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2021-06-28 11:44 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=20210628214430.6b3607d5@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mturquette@baylibre$(echo .)com \
    --cc=robert.hancock@calian$(echo .)com \
    --cc=sboyd@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox