From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: drivers/powercap/dtpm.c:602: warning: Function parameter or member 'dtpm_match_table' not described in 'dtpm_create_hierarchy'
Date: Sun, 10 Sep 2023 12:09:36 +0800 [thread overview]
Message-ID: <202309101242.EjuX7vK3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a3c57ab79a06e333a869ae340420cb3c6f5921d3
commit: 3759ec678e8944dc2ea70cab77a300408f78ae27 powercap/drivers/dtpm: Add hierarchy creation
date: 1 year, 7 months ago
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20230910/202309101242.EjuX7vK3-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230910/202309101242.EjuX7vK3-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/202309101242.EjuX7vK3-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/powercap/dtpm.c:602: warning: Function parameter or member 'dtpm_match_table' not described in 'dtpm_create_hierarchy'
>> drivers/powercap/dtpm.c:602: warning: Excess function parameter 'hierarchy' description in 'dtpm_create_hierarchy'
vim +602 drivers/powercap/dtpm.c
574
575 /**
576 * dtpm_create_hierarchy - Create the dtpm hierarchy
577 * @hierarchy: An array of struct dtpm_node describing the hierarchy
578 *
579 * The function is called by the platform specific code with the
580 * description of the different node in the hierarchy. It creates the
581 * tree in the sysfs filesystem under the powercap dtpm entry.
582 *
583 * The expected tree has the format:
584 *
585 * struct dtpm_node hierarchy[] = {
586 * [0] { .name = "topmost", type = DTPM_NODE_VIRTUAL },
587 * [1] { .name = "package", .type = DTPM_NODE_VIRTUAL, .parent = &hierarchy[0] },
588 * [2] { .name = "/cpus/cpu0", .type = DTPM_NODE_DT, .parent = &hierarchy[1] },
589 * [3] { .name = "/cpus/cpu1", .type = DTPM_NODE_DT, .parent = &hierarchy[1] },
590 * [4] { .name = "/cpus/cpu2", .type = DTPM_NODE_DT, .parent = &hierarchy[1] },
591 * [5] { .name = "/cpus/cpu3", .type = DTPM_NODE_DT, .parent = &hierarchy[1] },
592 * [6] { }
593 * };
594 *
595 * The last element is always an empty one and marks the end of the
596 * array.
597 *
598 * Return: zero on success, a negative value in case of error. Errors
599 * are reported back from the underlying functions.
600 */
601 int dtpm_create_hierarchy(struct of_device_id *dtpm_match_table)
> 602 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-10 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 4:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-27 10:19 drivers/powercap/dtpm.c:602: warning: Function parameter or member 'dtpm_match_table' not described in 'dtpm_create_hierarchy' kernel test robot
2024-01-06 11:22 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=202309101242.EjuX7vK3-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ulf.hansson@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