linux-kernel - Re: linux-next: build failure after merge of 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <bce51c8f-56c2-3a44-b590-149627398b7a@linux.intel.com>
Date: Thu, 15 May 2025 11:32:53 +0300 (EEST)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Ingo Molnar <mingo@...nel.org>, 
    PDx86 ML <platform-driver-x86@...r.kernel.org>, 
    Suma Hegde <suma.hegde@....com>
cc: Hans de Goede <hdegoede@...hat.com>, Mark Gross <markgross@...nel.org>, 
    Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
    Linux Next Mailing List <linux-next@...r.kernel.org>, x86@...nel.org, 
    Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>, 
    Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the drivers-x86 tree

On Thu, 15 May 2025, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/platform/x86/amd/hsmp/hwmon.c: In function 'hsmp_hwmon_write':
> drivers/platform/x86/amd/hsmp/hwmon.c:38:16: error: implicit declaration of function 'hsmp_send_message' [-Wimplicit-function-declaration]
>    38 |         return hsmp_send_message(&msg);
>       |                ^~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   92c025db52bb ("platform/x86/amd/hsmp: Report power via hwmon sensors")
> 
> I have used the drivers-x86 tree from next-20250514 for today.

Hi Stephen,

This is a direct result of moving a pdx86 related header behind my back:

https://lore.kernel.org/all/20250413084144.3746608-5-mingo@kernel.org/

That change wasn't sent to the relevant MAINTAINERS entries (and obviously 
then does not contain my ack either).

Ingo, any suggestion how to deal with this breakage? Do you have e.g. an 
IB which I could pull into pdx86 tree which has only these header moves?

-- 
 i.