linux-kernel - Re: [PATCH] cpufreq: qcom-nvmem: fix compilation warning for qcom_cpufreq_ipq806x_match

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <632sxqm4vxqg2e5aetuoakl5kkjb5x4zsyrdzqes7ylutiokxy@6tejdqp5x6ko>
Date: Thu, 20 Nov 2025 20:30:08 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Ilia Lin <ilia.lin@...nel.org>, 
	"Rafael J. Wysocki" <rafael@...nel.org>, Konrad Dybcio <konrad.dybcio@....qualcomm.com>, 
	linux-pm@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] cpufreq: qcom-nvmem: fix compilation warning for
 qcom_cpufreq_ipq806x_match_list

On 20-11-25, 14:35, Christian Marangi wrote:
> If CONFIG_OF is not enabled, of_match_node() is set as NULL and
> qcom_cpufreq_ipq806x_match_list won't be used causing a compilation
> warning.
> 
> Flag qcom_cpufreq_ipq806x_match_list as __maybe_unused to fix the
> compilation warning.
> 
> While at it also flag as __initconst as it's used only in probe contest
> and can be freed after probe.
> 
> This follows the pattern of the usual of_device_id variables.
> 
> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202511202119.6zvvFMup-lkp@intel.com/
> Fixes: 58f5d39d5ed8 ("cpufreq: qcom-nvmem: add compatible fallback for ipq806x for no SMEM")
> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>
> ---
>  drivers/cpufreq/qcom-cpufreq-nvmem.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied. Thanks.

-- 
viresh