* linux-next: Fixes tag needs some work in the extcon tree
@ 2025-09-08 6:03 Stephen Rothwell
2025-09-08 6:15 ` Randy Dunlap
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2025-09-08 6:03 UTC (permalink / raw)
To: Chanwoo Choi
Cc: Randy Dunlap, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: Fixes tag needs some work in the extcon tree
2025-09-08 6:03 linux-next: Fixes tag needs some work in the extcon tree Stephen Rothwell
@ 2025-09-08 6:15 ` Randy Dunlap
2025-09-08 8:19 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2025-09-08 6:15 UTC (permalink / raw)
To: Stephen Rothwell, Chanwoo Choi
Cc: Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: Fixes tag needs some work in the extcon tree
2025-09-08 6:15 ` Randy Dunlap
@ 2025-09-08 8:19 ` Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2025-09-08 8:19 UTC (permalink / raw)
To: Randy Dunlap
Cc: Chanwoo Choi, Linux Kernel Mailing List, Linux Next Mailing List
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-09-08 8:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-08 6:03 linux-next: Fixes tag needs some work in the extcon tree Stephen Rothwell
2025-09-08 6:15 ` Randy Dunlap
2025-09-08 8:19 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox