linux-kernel - Re: linux-next: Fixes tag needs some work in the drivers-x86 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: <4ad0f4f7-417d-4668-a0d8-ceef13814483@redhat.com>
Date: Wed, 20 Nov 2024 15:02:33 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Mark Gross <markgross@...nel.org>
Cc: 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 drivers-x86 tree

Hi,

On 18-Nov-24 10:06 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   c6a2b4fcec5f ("platform/x86: p2sb: Cache correct PCI bar for P2SB on Gemini Lake")
> 
> Fixes tag
> 
>   Fixes: 2841631a0365 ("platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: b28ff7a7c324 ("platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe")

Sorry I don't know where that wrong hash came from.

The suggested replacement hash is correct.

But I see that Ilpo has already tagged things and send out
a pull-request so I'm afraid it is too late to fix this one.

Regards,

Hans