* linux-next: Fixes tags need some work in the watchdog tree
@ 2022-01-03 21:36 Stephen Rothwell
2022-01-04 8:06 ` Andrej Picej
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2022-01-03 21:36 UTC (permalink / raw)
To: Wim Van Sebroeck
Cc: Sam Protsenko, Andrej Picej, Linux Kernel Mailing List,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Hi all,
In commit
02d04e694fa3 ("watchdog: s3c2410: Fix getting the optional clock")
Fixes tag
Fixes: a4f3dc8d5fbc ("watchdog: s3c2410: Support separate source clock")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: e249d01b5e8b ("watchdog: s3c2410: Support separate source clock")
In commit
ce3401c72f01 ("watchdog: da9063: Add hard dependency on I2C")
Fixes tag
Fixes: 5ea29919c294 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 968011a291f3 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
--
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 tags need some work in the watchdog tree
2022-01-03 21:36 linux-next: Fixes tags need some work in the watchdog tree Stephen Rothwell
@ 2022-01-04 8:06 ` Andrej Picej
2022-01-05 10:43 ` Wim Van Sebroeck
0 siblings, 1 reply; 3+ messages in thread
From: Andrej Picej @ 2022-01-04 8:06 UTC (permalink / raw)
To: Stephen Rothwell, Wim Van Sebroeck
Cc: Sam Protsenko, Linux Kernel Mailing List, Linux Next Mailing List
Hi Stephan,
On 3. 01. 22 22:36, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 02d04e694fa3 ("watchdog: s3c2410: Fix getting the optional clock")
>
> Fixes tag
>
> Fixes: a4f3dc8d5fbc ("watchdog: s3c2410: Support separate source clock")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: e249d01b5e8b ("watchdog: s3c2410: Support separate source clock")
>
> In commit
>
> ce3401c72f01 ("watchdog: da9063: Add hard dependency on I2C")
>
> Fixes tag
>
> Fixes: 5ea29919c294 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 968011a291f3 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
>
Yes, that's probably right for my patch, sorry for that.
I was puzzled on where to get the SHA1 of not-yet applied commit,
because this patches ("watchdog: da9063: use atomic safe i2c transfer in
reset handler" and the fix "watchdog: da9063: Add hard dependency on
I2C") followed quite closely together. Is there any way that I can get
the SHA1 of the commit that was applied? It should be a part of some
branch right? I'm asking because I couldn't find a repo or a branch that
this two commits are a part of.
Anyway should I send a v2, or what is the procedure here?
Thanks,
Andrej
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: linux-next: Fixes tags need some work in the watchdog tree
2022-01-04 8:06 ` Andrej Picej
@ 2022-01-05 10:43 ` Wim Van Sebroeck
0 siblings, 0 replies; 3+ messages in thread
From: Wim Van Sebroeck @ 2022-01-05 10:43 UTC (permalink / raw)
To: Andrej Picej
Cc: Stephen Rothwell, Sam Protsenko, Linux Kernel Mailing List,
Linux Next Mailing List
Hi All,
> Hi Stephan,
>
> On 3. 01. 22 22:36, Stephen Rothwell wrote:
> >Hi all,
> >
> >In commit
> >
> > 02d04e694fa3 ("watchdog: s3c2410: Fix getting the optional clock")
> >
> >Fixes tag
> >
> > Fixes: a4f3dc8d5fbc ("watchdog: s3c2410: Support separate source clock")
> >
> >has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> >Maybe you meant
> >
> >Fixes: e249d01b5e8b ("watchdog: s3c2410: Support separate source clock")
> >
> >In commit
> >
> > ce3401c72f01 ("watchdog: da9063: Add hard dependency on I2C")
> >
> >Fixes tag
> >
> > Fixes: 5ea29919c294 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
> >
> >has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> >Maybe you meant
> >
> >Fixes: 968011a291f3 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")
> >
>
> Yes, that's probably right for my patch, sorry for that.
>
> I was puzzled on where to get the SHA1 of not-yet applied commit,
> because this patches ("watchdog: da9063: use atomic safe i2c
> transfer in reset handler" and the fix "watchdog: da9063: Add hard
> dependency on I2C") followed quite closely together. Is there any
> way that I can get the SHA1 of the commit that was applied? It
> should be a part of some branch right? I'm asking because I couldn't
> find a repo or a branch that this two commits are a part of.
>
> Anyway should I send a v2, or what is the procedure here?
I'll fix that.
Kind reards,
Wim.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-05 10:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-01-03 21:36 linux-next: Fixes tags need some work in the watchdog tree Stephen Rothwell
2022-01-04 8:06 ` Andrej Picej
2022-01-05 10:43 ` Wim Van Sebroeck
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox