From: kernel test robot <lkp@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: drivers/cpuidle/governors/ladder.c:54: warning: Function parameter or member 'dev' not described in 'ladder_do_selection'
Date: Sun, 3 Dec 2023 23:48:42 +0800 [thread overview]
Message-ID: <202312032330.fMc5ODUJ-lkp@intel.com> (raw)
Hi Marcelo,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 33cc938e65a98f1d29d0a18403dbbee050dcad9a
commit: 7d4daeedd575bbc3c40c87fc6708a8b88c50fe7e governors: unify last_state_idx
date: 4 years, 4 months ago
config: x86_64-randconfig-r015-20230805 (https://download.01.org/0day-ci/archive/20231203/202312032330.fMc5ODUJ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231203/202312032330.fMc5ODUJ-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/202312032330.fMc5ODUJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpuidle/governors/ladder.c:54: warning: Function parameter or member 'dev' not described in 'ladder_do_selection'
vim +54 drivers/cpuidle/governors/ladder.c
4f86d3a8e29720 Len Brown 2007-10-03 44
4f86d3a8e29720 Len Brown 2007-10-03 45 /**
4f86d3a8e29720 Len Brown 2007-10-03 46 * ladder_do_selection - prepares private data for a state change
4f86d3a8e29720 Len Brown 2007-10-03 47 * @ldev: the ladder device
4f86d3a8e29720 Len Brown 2007-10-03 48 * @old_idx: the current state index
4f86d3a8e29720 Len Brown 2007-10-03 49 * @new_idx: the new target state index
4f86d3a8e29720 Len Brown 2007-10-03 50 */
7d4daeedd575bb Marcelo Tosatti 2019-07-03 51 static inline void ladder_do_selection(struct cpuidle_device *dev,
7d4daeedd575bb Marcelo Tosatti 2019-07-03 52 struct ladder_device *ldev,
4f86d3a8e29720 Len Brown 2007-10-03 53 int old_idx, int new_idx)
4f86d3a8e29720 Len Brown 2007-10-03 @54 {
4f86d3a8e29720 Len Brown 2007-10-03 55 ldev->states[old_idx].stats.promotion_count = 0;
4f86d3a8e29720 Len Brown 2007-10-03 56 ldev->states[old_idx].stats.demotion_count = 0;
7d4daeedd575bb Marcelo Tosatti 2019-07-03 57 dev->last_state_idx = new_idx;
4f86d3a8e29720 Len Brown 2007-10-03 58 }
4f86d3a8e29720 Len Brown 2007-10-03 59
:::::: The code at line 54 was first introduced by commit
:::::: 4f86d3a8e297205780cca027e974fd5f81064780 cpuidle: consolidate 2.6.22 cpuidle branch into one patch
:::::: TO: Len Brown <len.brown@intel.com>
:::::: CC: Len Brown <len.brown@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-03 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 15:48 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 8:52 drivers/cpuidle/governors/ladder.c:54: warning: Function parameter or member 'dev' not described in 'ladder_do_selection' kernel test robot
2023-11-12 2:55 kernel test robot
2023-10-21 17:41 kernel test robot
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=202312032330.fMc5ODUJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjw@rjwysocki.net \
/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