2024-03-05 00:09:37

by Stephen Rothwell

[permalink] [raw]
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


Attachments:
(No filename) (499.00 B)
OpenPGP digital signature

2024-03-05 04:35:44

by Viresh Kumar

[permalink] [raw]
Subject: Re: linux-next: build failure after merge of the cpufreq-arm tree

On 05-03-24, 11:09, Stephen Rothwell wrote:
> 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.

Sorry about that, dropped now.

--
viresh