linux-kernel - Re: linux-next: Fixes tags need some work in the watchdog tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <432b6c61-f8c6-368d-2386-590bed2aee7a@norik.com>
Date:   Tue, 4 Jan 2022 09:06:44 +0100
From:   Andrej Picej <andrej.picej@...ik.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Wim Van Sebroeck <wim@...ana.be>
Cc:     Sam Protsenko <semen.protsenko@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the watchdog tree

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