[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ddf0bd24-4e03-4346-84b7-c5caad8d885f@infradead.org>
Date: Sun, 7 Sep 2025 23:15:48 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Chanwoo Choi <cw00.choi@...sung.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the extcon tree
On 9/7/25 11:03 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 9f65e74d9185 ("extcon: max14526: avoid defined but not used warning")
>
> Fixes tag
>
> Fixes: 45af3ddd1cd ("extcon: Add basic support for Maxim MAX14526 MUIC")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 145af3ddd1cd ("extcon: Add basic support for Maxim MAX14526 MUIC")
Is that a real commit ID? I don't find it.
My email said this:
Fixes: c2aeb8647e53 ("extcon: Add basic support for Maxim MAX14526 MUIC")
(see https://lore.kernel.org/lkml/20250513210252.1139749-1-rdunlap@infradead.org/)
Maybe some commit IDs are not stable?
--
~Randy
Powered by blists - more mailing lists