From: kernel test robot <lkp@intel.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Dmitry Baryshkov <lumag@kernel.org>
Subject: [lumag-msm:venus-8996-vmem 70/173] Warning: drivers/cpufreq/qcom-cpufreq-hw.c:118 function parameter 'cpu_dev' not described in 'qcom_cpufreq_update_opp'
Date: Thu, 22 Oct 2026 13:28:10 +0800 [thread overview]
Message-ID: <202610221320.83iuWIYk-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/lumag/msm venus-8996-vmem
head: 4dff7b31dd13e97b8f7abab7bc115d2875afd5e8
commit: cfa31c4bc448f8442d713de3c9aedba5d810ac88 [70/173] cpufreq: qcom-hw: Add kerneldoc to some functions
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20261022/202610221320.83iuWIYk-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261022/202610221320.83iuWIYk-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/202610221320.83iuWIYk-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/cpufreq/qcom-cpufreq-hw.c:118 function parameter 'cpu_dev' not described in 'qcom_cpufreq_update_opp'
>> Warning: drivers/cpufreq/qcom-cpufreq-hw.c:118 Excess function parameter 'policy' description in 'qcom_cpufreq_update_opp'
>> Warning: drivers/cpufreq/qcom-cpufreq-hw.c:118 function parameter 'cpu_dev' not described in 'qcom_cpufreq_update_opp'
>> Warning: drivers/cpufreq/qcom-cpufreq-hw.c:118 Excess function parameter 'policy' description in 'qcom_cpufreq_update_opp'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-22 5:29 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=202610221320.83iuWIYk-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=llvm@lists.linux.dev \
--cc=lumag@kernel.org \
--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.