[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xdi2mu2i5yu3a57g5cla5vyvpjbrazxuzdqpvc37lk7lnf4uuj@czcpd2eu3peq>
Date: Fri, 21 Nov 2025 10:22:02 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christian Marangi <ansuelsmth@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the cpufreq-arm tree
On 21-11-25, 12:04, Stephen Rothwell wrote:
> Hi all,
>
> After merging the cpufreq-arm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: qcom_cpufreq_ipq8064_name_version+0x140 (section: .text) -> qcom_cpufreq_ipq806x_match_list (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: qcom_cpufreq_ipq8064_name_version+0x144 (section: .text) -> qcom_cpufreq_ipq806x_match_list (section: .init.rodata)
>
> Introduced by commit
>
> 0194066ac1ca ("cpufreq: qcom-nvmem: fix compilation warning for qcom_cpufreq_ipq806x_match_list")
Fixed and pushed.
diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
index 6c3c125f6818..81e16b5a0245 100644
--- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
+++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
@@ -256,7 +256,7 @@ static int qcom_cpufreq_krait_name_version(struct device *cpu_dev,
return ret;
}
-static const struct of_device_id qcom_cpufreq_ipq806x_match_list[] __initconst __maybe_unused = {
+static const struct of_device_id qcom_cpufreq_ipq806x_match_list[] __maybe_unused = {
{ .compatible = "qcom,ipq8062", .data = (const void *)QCOM_ID_IPQ8062 },
{ .compatible = "qcom,ipq8064", .data = (const void *)QCOM_ID_IPQ8064 },
{ .compatible = "qcom,ipq8065", .data = (const void *)QCOM_ID_IPQ8065 },
--
viresh
Powered by blists - more mailing lists