linux-kernel - Re: linux-next: Fixes tag needs some work in the printk 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] [day] [month] [year] [list]

Date:   Tue, 3 Nov 2020 09:46:06 +0100
From:   Petr Mladek <pmladek@...e.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>,
        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 printk tree

On Tue 2020-11-03 08:32:01, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   8a8424bf2439 ("init/Kconfig: Fix CPU number in LOG_CPU_MAX_BUF_SHIFT description")
> 
> Fixes tag
> 
>   Fixes: 23b2899f7f ("printk: allow increasing the ring buffer depending on the number of CPUs")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed 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").

Should be fixed now. It is a pity that checkpatch.pl did not warn
about it.

Thanks for the report.

Best Regards,
Petr