From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linus.walleij@linaro.org, gnurou@gmail.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: Re: [PATCH 5/5] gpio: ws16c48: Add support for GPIO names
Date: Tue, 31 Jan 2017 01:59:49 +0800 [thread overview]
Message-ID: <201701310102.1vagmj0R%fengguang.wu@intel.com> (raw)
In-Reply-To: <edb689aac0bd4bb2b119dc8216da7cfb6af5243b.1485795642.git.vilhelm.gray@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
Hi William,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on next-20170130]
[cannot apply to v4.10-rc6]
[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/William-Breathitt-Gray/gpio-Add-support-for-GPIO-names-for-several-ISA_BUS_API-drivers/20170131-013038
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: i386-randconfig-x003-201705 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/gpio/gpio-ws16c48.c: In function 'ws16c48_probe':
>> drivers/gpio/gpio-ws16c48.c:381:28: error: 'ws16c48_names' undeclared (first use in this function)
ws16c48gpio->chip.names = ws16c48_names;
^~~~~~~~~~~~~
drivers/gpio/gpio-ws16c48.c:381:28: note: each undeclared identifier is reported only once for each function it appears in
At top level:
drivers/gpio/gpio-ws16c48.c:345:20: warning: 'ws14c48_names' defined but not used [-Wunused-variable]
static const char *ws14c48_names[WS16C48_NGPIO] = {
^~~~~~~~~~~~~
vim +/ws16c48_names +381 drivers/gpio/gpio-ws16c48.c
375
376 ws16c48gpio->chip.label = name;
377 ws16c48gpio->chip.parent = dev;
378 ws16c48gpio->chip.owner = THIS_MODULE;
379 ws16c48gpio->chip.base = -1;
380 ws16c48gpio->chip.ngpio = WS16C48_NGPIO;
> 381 ws16c48gpio->chip.names = ws16c48_names;
382 ws16c48gpio->chip.get_direction = ws16c48_gpio_get_direction;
383 ws16c48gpio->chip.direction_input = ws16c48_gpio_direction_input;
384 ws16c48gpio->chip.direction_output = ws16c48_gpio_direction_output;
---
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: 18101 bytes --]
prev parent reply other threads:[~2017-01-30 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 17:04 [PATCH 0/5] gpio: Add support for GPIO names for several ISA_BUS_API drivers William Breathitt Gray
2017-01-30 17:05 ` [PATCH 1/5] gpio: 104-dio-48e: Add support for GPIO names William Breathitt Gray
2017-01-30 17:05 ` [PATCH 2/5] gpio: 104-idi-48: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 3/5] gpio: 104-idio-16: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 4/5] gpio: gpio-mm: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 5/5] gpio: ws16c48: " William Breathitt Gray
2017-01-30 17:59 ` kbuild test robot [this message]
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=201701310102.1vagmj0R%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=gnurou@gmail.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@gmail.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).