From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Felix Gu <gu_0233@qq.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the spi tree
Date: Wed, 14 Jan 2026 08:41:23 +1100 [thread overview]
Message-ID: <20260114084123.7a3fc1b1@canb.auug.org.au> (raw)
In-Reply-To: <20260114083730.4e405e1f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hi all,
On Wed, 14 Jan 2026 08:37:30 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> In commit
>
> 383d4f5cffcc ("spi: spi-sprd-adi: Fix double free in probe error path")
>
> Fixes tag
>
> Fixes: ac17750 ("spi: sprd: Add the support of restarting the system")
>
> 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").
This is actually in the spi-fixes tree, sorry.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-01-13 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 21:37 Stephen Rothwell
2026-01-13 21:41 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-19 21:44 Stephen Rothwell
2024-02-19 22:48 ` Randy Dunlap
2024-02-19 22:54 ` Mark Brown
2022-03-17 21:18 Stephen Rothwell
2022-03-18 7:10 ` Biju Das
2022-03-18 15:44 ` Mark Brown
2022-03-18 15:48 ` Biju Das
2021-05-11 22:24 Stephen Rothwell
2021-04-11 22:37 Stephen Rothwell
2021-01-11 20:36 Stephen Rothwell
2021-01-11 20:58 ` Pratyush Yadav
2021-01-11 23:00 ` Mark Brown
2019-04-01 18:12 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=20260114084123.7a3fc1b1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=gu_0233@qq.com \
--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
all inboxes | Powered by JetHome®