From: kernel test robot <lkp@intel.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: drivers/cpufreq/s3c64xx-cpufreq.c:55:22: warning: variable 'old_freq' set but not used
Date: Sun, 19 Jan 2025 18:39:30 +0800 [thread overview]
Message-ID: <202501191803.CtfT7b2o-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fda5e3f284002ea55dac1c98c1498d6dd684046e
commit: 81746019b9fbb9fbf7c522dcbeefb572ac0f9458 cpufreq: Drop CONFIG_ARM and CONFIG_ARM64 dependency on Arm drivers
date: 5 months ago
config: sh-randconfig-m031-20230725 (https://download.01.org/0day-ci/archive/20250119/202501191803.CtfT7b2o-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250119/202501191803.CtfT7b2o-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501191803.CtfT7b2o-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/cpufreq/s3c64xx-cpufreq.c: In function 's3c64xx_cpufreq_set_target':
>> drivers/cpufreq/s3c64xx-cpufreq.c:55:22: warning: variable 'old_freq' set but not used [-Wunused-but-set-variable]
55 | unsigned int old_freq, new_freq;
| ^~~~~~~~
>> drivers/cpufreq/s3c64xx-cpufreq.c:54:30: warning: variable 'dvfs' set but not used [-Wunused-but-set-variable]
54 | struct s3c64xx_dvfs *dvfs;
| ^~~~
vim +/old_freq +55 drivers/cpufreq/s3c64xx-cpufreq.c
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 50
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 51 static int s3c64xx_cpufreq_set_target(struct cpufreq_policy *policy,
9c0ebcf78fde0f drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2013-10-25 52 unsigned int index)
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 53 {
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 @54 struct s3c64xx_dvfs *dvfs;
d4019f0a92ab80 drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2013-08-14 @55 unsigned int old_freq, new_freq;
d4019f0a92ab80 drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2013-08-14 56 int ret;
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 57
652ed95d5fa607 drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2014-01-09 58 old_freq = clk_get_rate(policy->clk) / 1000;
d4019f0a92ab80 drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2013-08-14 59 new_freq = s3c64xx_freq_table[index].frequency;
9c0ebcf78fde0f drivers/cpufreq/s3c64xx-cpufreq.c Viresh Kumar 2013-10-25 60 dvfs = &s3c64xx_dvfs_table[s3c64xx_freq_table[index].driver_data];
b3748ddd80569e arch/arm/plat-s3c64xx/cpufreq.c Mark Brown 2009-06-15 61
:::::: The code at line 55 was first introduced by commit
:::::: d4019f0a92ab802f385cc9c8ad3ab7b5449712cb cpufreq: move freq change notifications to cpufreq core
:::::: TO: Viresh Kumar <viresh.kumar@linaro.org>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-19 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202501191803.CtfT7b2o-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome