linux-kernel - Re: linux-next: build failure after merge of the scmi 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250502-aquatic-grebe-of-infinity-fbf10e@sudeepholla>
Date: Fri, 2 May 2025 10:44:05 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Cristian Marussi <cristian.marussi@....com>,
	Sudeep Holla <sudeep.holla@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the scmi tree

On Fri, May 02, 2025 at 07:37:08PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the scmi tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/firmware/arm_scmi/quirks.c: In function 'scmi_quirk_signature':
> drivers/firmware/arm_scmi/quirks.c:208:24: error: implicit declaration of function 'partial_name_hash' [-Wimplicit-function-declaration]
>   208 |                 hash = partial_name_hash(tolower(*p++), hash);
>       |                        ^~~~~~~~~~~~~~~~~
> drivers/firmware/arm_scmi/quirks.c:209:18: error: implicit declaration of function 'end_name_hash' [-Wimplicit-function-declaration]
>   209 |         hash32 = end_name_hash(hash);
>       |                  ^~~~~~~~~~~~~
> drivers/firmware/arm_scmi/quirks.c:211:9: error: implicit declaration of function 'kfree' [-Wimplicit-function-declaration]
>   211 |         kfree(signature);
>       |         ^~~~~
> 
> Caused by commit
> 
>   81ce8d705821 ("firmware: arm_scmi: Add common framework to handle firmware quirks")
> 
> I have disabled CONFIG_ARM_SCMI_QUIRKS for today.

Thanks for the report and just disabling CONFIG_ARM_SCMI_QUIRKS for now.
We will get it fixed before next linux-next merge.

-- 
Regards,
Sudeep