Re: linux-next: Fixes tag needs some work in the extcon tree

[Stephen Rothwell <sfr@canb.auug.org.au>]

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

Hi Randy,

On Sun, 7 Sep 2025 23:15:48 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 9/7/25 11:03 PM, Stephen Rothwell wrote:
> > 
> > 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?

I have:

$ git branch -l -r --contains 145af3ddd1cd
  extcon/extcon-next
$ git branch -l -r --contains c2aeb8647e53
<nothing>

So I guess the extcon branch was rebased and 145af3ddd1cd will be in
today's liux-next.

-- 
Cheers,
Stephen Rothwell

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