[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250908181948.283dfbd8@canb.auug.org.au>
Date: Mon, 8 Sep 2025 18:19:48 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Chanwoo Choi <cw00.choi@...sung.com>, 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
Hi Randy,
On Sun, 7 Sep 2025 23:15:48 -0700 Randy Dunlap <rdunlap@...radead.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
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists