From: kbuild test robot <lkp@intel.com>
To: Nandor Han <nandor.han@ge.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
davem@davemloft.net, geert@linux-m68k.org, mchehab@kernel.org,
daniel.vetter@ffwll.ch, linus.walleij@linaro.org,
gnurou@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Nandor Han <nandor.han@ge.com>,
Semi Malinen <semi.malinen@ge.com>
Subject: Re: [PATCH v2 2/4] gpio - Add EXAR XRA1403 SPI GPIO expander driver
Date: Fri, 14 Apr 2017 00:22:06 +0800 [thread overview]
Message-ID: <201704140028.4r21UP3N%fengguang.wu@intel.com> (raw)
In-Reply-To: <f28eef264102786357ac5ed7205813619c508fb4.1492077070.git.nandor.han@ge.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
Hi Nandor,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.11-rc6 next-20170413]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Nandor-Han/XRA1403-gpio-add-XRA1403-gpio-expander-driver/20170413-215739
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: frv-allyesconfig (attached as .config)
compiler: frv-linux-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=frv
All errors (new ones prefixed by >>):
drivers//gpio/gpio-xra1403.c: In function 'xra1403_dbg_show':
>> drivers//gpio/gpio-xra1403.c:133:2: error: implicit declaration of function 'seq_puts' [-Werror=implicit-function-declaration]
seq_puts(s, "xra reg:");
^~~~~~~~
>> drivers//gpio/gpio-xra1403.c:135:3: error: implicit declaration of function 'seq_printf' [-Werror=implicit-function-declaration]
seq_printf(s, " %2.2x", reg);
^~~~~~~~~~
cc1: some warnings being treated as errors
vim +/seq_puts +133 drivers//gpio/gpio-xra1403.c
127 struct xra1403 *xra = gpiochip_get_data(chip);
128 int value[xra1403_regmap_cfg.max_register];
129 int i;
130 unsigned int gcr;
131 unsigned int gsr;
132
> 133 seq_puts(s, "xra reg:");
134 for (reg = 0; reg <= xra1403_regmap_cfg.max_register; reg++)
> 135 seq_printf(s, " %2.2x", reg);
136 seq_puts(s, "\n value:");
137 for (reg = 0; reg < xra1403_regmap_cfg.max_register; reg++) {
138 regmap_read(xra->regmap, reg, &value[reg]);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47568 bytes --]
next prev parent reply other threads:[~2017-04-13 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 10:27 [PATCH v2 0/4] XRA1403,gpio - add XRA1403 gpio expander driver Nandor Han
2017-04-13 10:27 ` [PATCH v2 1/4] dt-bindings: gpio - add exar to vendor prefixes list Nandor Han
2017-04-19 21:48 ` Rob Herring
2017-04-24 13:19 ` Linus Walleij
2017-04-13 10:27 ` [PATCH v2 2/4] gpio - Add EXAR XRA1403 SPI GPIO expander driver Nandor Han
2017-04-13 16:22 ` kbuild test robot [this message]
2017-04-24 13:47 ` Linus Walleij
2017-04-24 13:53 ` Han, Nandor (GE Healthcare)
2017-04-25 7:07 ` Benjamin Henrion
2017-04-25 7:15 ` Geert Uytterhoeven
2017-04-26 17:50 ` Andy Shevchenko
2017-04-26 14:42 ` Linus Walleij
2017-04-13 10:27 ` [PATCH v2 3/4] doc,dts - add XRA1403 DTS binding documentation Nandor Han
2017-04-19 21:55 ` Rob Herring
2017-04-24 13:49 ` Linus Walleij
2017-04-13 10:27 ` [PATCH v2 4/4] Add XRA1403 support to MAINTAINERS file Nandor Han
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=201704140028.4r21UP3N%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=nandor.han@ge.com \
--cc=robh+dt@kernel.org \
--cc=semi.malinen@ge.com \
/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).