From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: drivers/gpio/gpio-sim.c:839:2: warning: There is an unknown macro here somewhere. Configuration is required. If fwnode_for_each_child_node is a macro then please configure it. [unknownMacro]
Date: Fri, 01 Apr 2022 06:20:45 +0800 [thread overview]
Message-ID: <202204010621.wWp6WwgS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
CC: linux-kernel(a)vger.kernel.org
TO: Bartosz Golaszewski <brgl@bgdev.pl>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 787af64d05cd528aac9ad16752d11bb1c6061bb9
commit: cb8c474e79be458f58e9df073f51ca159f3a2aa0 gpio: sim: new testing module
date: 3 months ago
:::::: branch date: 23 hours ago
:::::: commit date: 3 months ago
compiler: ia64-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> drivers/gpio/gpiolib-acpi.c:252:2: warning: There is an unknown macro here somewhere. Configuration is required. If list_for_each_entry is a macro then please configure it. [unknownMacro]
list_for_each_entry(event, &acpi_gpio->events, node)
^
--
>> drivers/gpio/gpio-sim.c:839:2: warning: There is an unknown macro here somewhere. Configuration is required. If fwnode_for_each_child_node is a macro then please configure it. [unknownMacro]
fwnode_for_each_child_node(swnode, child)
^
vim +839 drivers/gpio/gpio-sim.c
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 834
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 835 static void gpio_sim_remove_swnode_recursive(struct fwnode_handle *swnode)
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 836 {
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 837 struct fwnode_handle *child;
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 838
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 @839 fwnode_for_each_child_node(swnode, child)
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 840 fwnode_remove_software_node(child);
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 841
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 842 fwnode_remove_software_node(swnode);
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 843 }
cb8c474e79be45 Bartosz Golaszewski 2021-12-07 844
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-31 22:20 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=202204010621.wWp6WwgS-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 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.