All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Liao Chen <liaochen4@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 1942/1942] drivers/cpufreq/brcmstb-avs-cpufreq.c:458:9: warning: ISO C90 forbids mixed declarations and code
Date: Sat, 13 Dec 2025 20:50:26 +0800	[thread overview]
Message-ID: <202512132042.PgSubudu-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head:   5a399b91821faeec2466751db2d714b24f8eb17c
commit: 5bfdf47235f04f1d6e51aa8381e804c3160d834b [1942/1942] cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value
config: arm64-randconfig-r071-20251213 (https://download.01.org/0day-ci/archive/20251213/202512132042.PgSubudu-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512132042.PgSubudu-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/202512132042.PgSubudu-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/cpufreq/brcmstb-avs-cpufreq.c: In function 'brcm_avs_cpufreq_get':
>> drivers/cpufreq/brcmstb-avs-cpufreq.c:458:9: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
     458 |         struct private_data *priv = policy->driver_data;
         |         ^~~~~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for HARDLOCKUP_DETECTOR
   Depends on [n]: DEBUG_KERNEL [=n] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=n] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=y])
   Selected by [y]:
   - SDEI_WATCHDOG [=y] && <choice> && ARM_SDE_INTERFACE [=y] && !HARDLOCKUP_CHECK_TIMESTAMP [=n]


vim +458 drivers/cpufreq/brcmstb-avs-cpufreq.c

de322e085995b9 Markus Mayer     2016-10-27  452  
de322e085995b9 Markus Mayer     2016-10-27  453  static unsigned int brcm_avs_cpufreq_get(unsigned int cpu)
de322e085995b9 Markus Mayer     2016-10-27  454  {
de322e085995b9 Markus Mayer     2016-10-27  455  	struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
5bfdf47235f04f Anastasia Belova 2024-05-07  456  	if (!policy)
5bfdf47235f04f Anastasia Belova 2024-05-07  457  		return 0;
de322e085995b9 Markus Mayer     2016-10-27 @458  	struct private_data *priv = policy->driver_data;
de322e085995b9 Markus Mayer     2016-10-27  459  
de322e085995b9 Markus Mayer     2016-10-27  460  	return brcm_avs_get_frequency(priv->base);
de322e085995b9 Markus Mayer     2016-10-27  461  }
de322e085995b9 Markus Mayer     2016-10-27  462  

:::::: The code at line 458 was first introduced by commit
:::::: de322e085995b9417582d6f72229dadb5c09d163 cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs

:::::: TO: Markus Mayer <mmayer@broadcom.com>
:::::: 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-12-13 12:50 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=202512132042.PgSubudu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=liaochen4@huawei.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.