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

Message-ID: <20240305110914.69ed133b@canb.auug.org.au>
Date: Tue, 5 Mar 2024 11:09:14 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>, Linux Kernel
 Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the cpufreq-arm tree

Hi all,

After merging the cpufreq-arm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

drivers/cpufreq/qcom-cpufreq-nvmem.c: In function 'qcom_cpufreq_kryo_name_version':
drivers/cpufreq/qcom-cpufreq-nvmem.c:194:14: error: 'QCOM_ID_IPQ5321' undeclared (first use in this function); did you mean 'QCOM_ID_IPQ5312'?
  194 |         case QCOM_ID_IPQ5321:
      |              ^~~~~~~~~~~~~~~
      |              QCOM_ID_IPQ5312

Caused by commit

  006af7c6958e ("cpufreq: qcom-nvmem: add support for IPQ5321")

I have used the cpufreq-arm tree from next-20240304 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped