linux-kernel - Re: linux-next: Fixes tag needs some work in the rockchip 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]

Message-ID: <2979372.e9J7NaK4W3@diego>
Date: Mon, 30 Sep 2024 15:55:33 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Sam Edwards <cfsworks@...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 tag needs some work in the rockchip tree

Am Montag, 30. September 2024, 15:36:34 CEST schrieb Stephen Rothwell:
> Hi all,
> 
> In commits
> 
>   ab3cf1ab3fdb ("arm64: dts: rockchip: Designate Turing RK1's system power controller")
>   ed1b30c33bb9 ("arm64: dts: rockchip: Fix Turing RK1 PCIe3 hang")
> 
> Fixes tag
> 
>   Fixes: 2806a69f3f ("arm64: dts: rockchip: Add Turing RK1 SoM support")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
> 
>     This can be fixed for the future 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").

I've fixed up the commits with more appropriate commit hashes