From: kernel test robot <lkp@intel.com>
To: Naresh Solanki <naresh.solanki@9elements.com>,
broonie@kernel.org, zev@bewilderbeest.net,
Liam Girdwood <lgirdwood@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Naresh Solanki <Naresh.Solanki@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] regulator: userspace-consumer: Retrieve supplies from DT
Date: Wed, 11 Oct 2023 00:47:17 +0800 [thread overview]
Message-ID: <202310110043.uMSq3kAw-lkp@intel.com> (raw)
In-Reply-To: <20231004121010.1192344-2-naresh.solanki@9elements.com>
Hi Naresh,
kernel test robot noticed the following build errors:
[auto build test ERROR on f9a1d31874c383f58bb4f89bfe79b764682cd026]
url: https://github.com/intel-lab-lkp/linux/commits/Naresh-Solanki/regulator-userspace-consumer-Retrieve-supplies-from-DT/20231004-201151
base: f9a1d31874c383f58bb4f89bfe79b764682cd026
patch link: https://lore.kernel.org/r/20231004121010.1192344-2-naresh.solanki%409elements.com
patch subject: [PATCH v2 2/3] regulator: userspace-consumer: Retrieve supplies from DT
config: x86_64-buildonly-randconfig-003-20231010 (https://download.01.org/0day-ci/archive/20231011/202310110043.uMSq3kAw-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/20231011/202310110043.uMSq3kAw-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/202310110043.uMSq3kAw-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/regulator/userspace-consumer.c: In function 'get_num_supplies':
drivers/regulator/userspace-consumer.c:139:9: error: implicit declaration of function 'for_each_property_of_node'; did you mean 'for_each_child_of_node'? [-Werror=implicit-function-declaration]
139 | for_each_property_of_node(pdev->dev.of_node, prop) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| for_each_child_of_node
drivers/regulator/userspace-consumer.c:139:59: error: expected ';' before '{' token
139 | for_each_property_of_node(pdev->dev.of_node, prop) {
| ^~
| ;
drivers/regulator/userspace-consumer.c:137:13: warning: unused variable 'num_supplies' [-Wunused-variable]
137 | int num_supplies = 0;
| ^~~~~~~~~~~~
>> drivers/regulator/userspace-consumer.c:144:1: error: no return statement in function returning non-void [-Werror=return-type]
144 | }
| ^
drivers/regulator/userspace-consumer.c: In function 'regulator_userspace_consumer_probe':
drivers/regulator/userspace-consumer.c:170:67: error: expected ';' before '{' token
170 | for_each_property_of_node(pdev->dev.of_node, prop) {
| ^~
| ;
drivers/regulator/userspace-consumer.c: At top level:
drivers/regulator/userspace-consumer.c:121:15: warning: 'prop_supply_name' defined but not used [-Wunused-function]
121 | static size_t prop_supply_name(char *prop_name)
| ^~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +144 drivers/regulator/userspace-consumer.c
133
134 static int get_num_supplies(struct platform_device *pdev)
135 {
136 struct property *prop;
137 int num_supplies = 0;
138
139 for_each_property_of_node(pdev->dev.of_node, prop) {
140 if (prop_supply_name(prop->name))
141 num_supplies++;
142 }
143 return num_supplies;
> 144 }
145
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-10 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 12:10 [PATCH v2 1/3] dt-bindings: regulator: regulator-output: Multiple supplies Naresh Solanki
2023-10-04 12:10 ` [PATCH v2 2/3] regulator: userspace-consumer: Retrieve supplies from DT Naresh Solanki
2023-10-04 18:11 ` kernel test robot
2023-10-10 16:47 ` kernel test robot [this message]
2023-10-04 12:10 ` [PATCH v2 3/3] regulator: userspace-consumer: Update name Naresh Solanki
2023-10-05 20:12 ` [PATCH v2 1/3] dt-bindings: regulator: regulator-output: Multiple supplies Krzysztof Kozlowski
2023-10-06 16:30 ` Rob Herring
2023-10-10 17:30 ` Mark Brown
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=202310110043.uMSq3kAw-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zev@bewilderbeest.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 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.