linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the cpufreq-arm tree
@ 2024-03-05  0:09 Stephen Rothwell
  2024-03-05  4:35 ` Viresh Kumar
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2024-03-05  0:09 UTC (permalink / raw)
  To: Viresh Kumar
  Cc: Kathiravan Thirumoorthy, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: build failure after merge of the cpufreq-arm tree
  2024-03-05  0:09 linux-next: build failure after merge of the cpufreq-arm tree Stephen Rothwell
@ 2024-03-05  4:35 ` Viresh Kumar
  0 siblings, 0 replies; 2+ messages in thread
From: Viresh Kumar @ 2024-03-05  4:35 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Kathiravan Thirumoorthy, Linux Kernel Mailing List,
	Linux Next Mailing List

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-03-05  4:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-05  0:09 linux-next: build failure after merge of the cpufreq-arm tree Stephen Rothwell
2024-03-05  4:35 ` Viresh Kumar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).