From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:irq/irq_chip_ro 3/9] drivers/irqchip/irq-mvebu-pic.c:74:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'?
Date: Mon, 31 Jan 2022 16:01:43 +0800 [thread overview]
Message-ID: <202201311519.CLOwt1F2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irq_chip_ro
head: f63a5ded3ea0cd2c587db00f89d219789fbee683
commit: a57739a1ce5301e34704447de96205450c3bf87d [3/9] irqchip/mvebu-pic: Switch to dynamic chip name output
config: arm64-buildonly-randconfig-r002-20220131 (https://download.01.org/0day-ci/archive/20220131/202201311519.CLOwt1F2-lkp@intel.com/config)
compiler: aarch64-linux-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/maz/arm-platforms.git/commit/?id=a57739a1ce5301e34704447de96205450c3bf87d
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms irq/irq_chip_ro
git checkout a57739a1ce5301e34704447de96205450c3bf87d
# 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=arm64 SHELL=/bin/bash drivers/
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 >>):
drivers/irqchip/irq-mvebu-pic.c: In function 'mvebu_pic_print_chip':
>> drivers/irqchip/irq-mvebu-pic.c:74:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'? [-Werror=implicit-function-declaration]
74 | seq_printf(p, "%s", dev_name(&pic->pdev->dev));
| ^~~~~~~~~~
| bstr_printf
cc1: some warnings being treated as errors
vim +74 drivers/irqchip/irq-mvebu-pic.c
69
70 static void mvebu_pic_print_chip(struct irq_data *d, struct seq_file *p)
71 {
72 struct mvebu_pic *pic = irq_data_get_irq_chip_data(d);
73
> 74 seq_printf(p, "%s", dev_name(&pic->pdev->dev));
75 }
76
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [arm-platforms:irq/irq_chip_ro 3/9] drivers/irqchip/irq-mvebu-pic.c:74:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'?
Date: Mon, 31 Jan 2022 16:01:43 +0800 [thread overview]
Message-ID: <202201311519.CLOwt1F2-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irq_chip_ro
head: f63a5ded3ea0cd2c587db00f89d219789fbee683
commit: a57739a1ce5301e34704447de96205450c3bf87d [3/9] irqchip/mvebu-pic: Switch to dynamic chip name output
config: arm64-buildonly-randconfig-r002-20220131 (https://download.01.org/0day-ci/archive/20220131/202201311519.CLOwt1F2-lkp(a)intel.com/config)
compiler: aarch64-linux-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/maz/arm-platforms.git/commit/?id=a57739a1ce5301e34704447de96205450c3bf87d
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms irq/irq_chip_ro
git checkout a57739a1ce5301e34704447de96205450c3bf87d
# 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=arm64 SHELL=/bin/bash drivers/
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 >>):
drivers/irqchip/irq-mvebu-pic.c: In function 'mvebu_pic_print_chip':
>> drivers/irqchip/irq-mvebu-pic.c:74:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'? [-Werror=implicit-function-declaration]
74 | seq_printf(p, "%s", dev_name(&pic->pdev->dev));
| ^~~~~~~~~~
| bstr_printf
cc1: some warnings being treated as errors
vim +74 drivers/irqchip/irq-mvebu-pic.c
69
70 static void mvebu_pic_print_chip(struct irq_data *d, struct seq_file *p)
71 {
72 struct mvebu_pic *pic = irq_data_get_irq_chip_data(d);
73
> 74 seq_printf(p, "%s", dev_name(&pic->pdev->dev));
75 }
76
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-01-31 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:01 kernel test robot [this message]
2022-01-31 8:01 ` [arm-platforms:irq/irq_chip_ro 3/9] drivers/irqchip/irq-mvebu-pic.c:74:9: error: implicit declaration of function 'seq_printf'; did you mean 'bstr_printf'? 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=202201311519.CLOwt1F2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.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 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.