From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4550/4901] drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:325:17: error: 'gc_parent' undeclared; did you mean 'xa_parent'?
Date: Thu, 10 Feb 2022 18:43:22 +0800 [thread overview]
Message-ID: <202202101846.4j5fV5nD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 395a61741f7ea29e1f4a0d6e160197fe8e377572
commit: 03182a20db448774a4cf5f2e5b1c4bd660746ebe [4550/4901] pinctrl: npcm: Fix broken references to chip->parent_device
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20220210/202202101846.4j5fV5nD-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=03182a20db448774a4cf5f2e5b1c4bd660746ebe
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 03182a20db448774a4cf5f2e5b1c4bd660746ebe
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/printk.h:555,
from include/asm-generic/bug.h:22,
from arch/arm/include/asm/bug.h:60,
from include/linux/bug.h:5,
from include/linux/thread_info.h:13,
from include/asm-generic/current.h:5,
from arch/arm/include/asm/current.h:50,
from include/linux/sched.h:12,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:5:
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c: In function 'npcmgpio_irq_startup':
>> drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:325:17: error: 'gc_parent' undeclared (first use in this function); did you mean 'xa_parent'?
325 | dev_dbg(gc_parent, "startup: %u.%u\n", gpio, d->irq);
| ^~~~~~~~~
include/linux/dynamic_debug.h:134:29: note: in definition of macro '__dynamic_func_call'
134 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:166:9: note: in expansion of macro '_dynamic_func_call'
166 | _dynamic_func_call(fmt,__dynamic_dev_dbg, \
| ^~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:155:9: note: in expansion of macro 'dynamic_dev_dbg'
155 | dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:325:9: note: in expansion of macro 'dev_dbg'
325 | dev_dbg(gc_parent, "startup: %u.%u\n", gpio, d->irq);
| ^~~~~~~
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:325:17: note: each undeclared identifier is reported only once for each function it appears in
325 | dev_dbg(gc_parent, "startup: %u.%u\n", gpio, d->irq);
| ^~~~~~~~~
include/linux/dynamic_debug.h:134:29: note: in definition of macro '__dynamic_func_call'
134 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:166:9: note: in expansion of macro '_dynamic_func_call'
166 | _dynamic_func_call(fmt,__dynamic_dev_dbg, \
| ^~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:155:9: note: in expansion of macro 'dynamic_dev_dbg'
155 | dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c:325:9: note: in expansion of macro 'dev_dbg'
325 | dev_dbg(gc_parent, "startup: %u.%u\n", gpio, d->irq);
| ^~~~~~~
vim +325 drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c
318
319 static unsigned int npcmgpio_irq_startup(struct irq_data *d)
320 {
321 struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
322 unsigned int gpio = d->hwirq;
323
324 /* active-high, input, clear interrupt, enable interrupt */
> 325 dev_dbg(gc_parent, "startup: %u.%u\n", gpio, d->irq);
326 npcmgpio_direction_input(gc, gpio);
327 npcmgpio_irq_ack(d);
328 npcmgpio_irq_unmask(d);
329
330 return 0;
331 }
332
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-10 10:43 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=202202101846.4j5fV5nD-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.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;
as well as URLs for NNTP newsgroup(s).