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]
Date:   Mon, 24 Jan 2022 12:52:12 +0100
From:   Ansuel Smith <ansuelsmth@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Boris Brezillon <boris.brezillon@...labora.com>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Miaoqian Lin <linmq006@...il.com>,
        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 mtd-fixes tree

On Mon, Jan 24, 2022 at 07:28:00AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   2b3d77cb5ce3 ("mtd: parsers: qcom: Fix kernel panic on skipped partition")
> 
> Fixes tag
> 
>   Fixes: 803eb12 ("mtd: parsers: Add Qcom SMEM parser")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed in the futrure by setting core.abbrev to 12 (or more)
>     or (for git v2.11 or later) just making sure it is not set (or set to
>     "auto").
> 
> In commit
> 
>   7815173a7ccb ("mtd: rawnand: ingenic: Fix missing put_device in ingenic_ecc_get")
> 
> Fixes tag
> 
>   Fixes: 15de8c6 ("mtd: rawnand: ingenic: Separate top-level and SoC specific code")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed in the futrure by setting core.abbrev to 12 (or more)
>     or (for git v2.11 or later) just making sure it is not set (or set to
>     "auto").
> 
> -- 
> Cheers,
> Stephen Rothwell

Hi, sorry for the mistake. I wrongly copied the Fixes tag from a prev
commit. Should I resend the series with the correct fixes? 

-- 
	Ansuel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ