From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH -next] Input: gpio_keys: set input direction explicitly for gpio keys
Date: Wed, 16 Nov 2016 20:48:38 +0800 [thread overview]
Message-ID: <201611162016.1LsBx0KB%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479297298-26555-1-git-send-email-sudeep.holla@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
Hi Sudeep,
[auto build test ERROR on next-20161116]
url: https://github.com/0day-ci/linux/commits/Sudeep-Holla/Input-gpio_keys-set-input-direction-explicitly-for-gpio-keys/20161116-202319
config: x86_64-randconfig-x017-201646 (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=x86_64
All errors (new ones prefixed by >>):
drivers/input/keyboard/gpio_keys.c: In function 'gpio_keys_setup_key':
>> drivers/input/keyboard/gpio_keys.c:506:4: error: 'flags' undeclared (first use in this function)
flags |= GPIOF_ACTIVE_LOW;
^~~~~
drivers/input/keyboard/gpio_keys.c:506:4: note: each undeclared identifier is reported only once for each function it appears in
vim +/flags +506 drivers/input/keyboard/gpio_keys.c
700a38b2 Dmitry Torokhov 2016-10-19 500 } else if (gpio_is_valid(button->gpio)) {
5feeca3c Geert Uytterhoeven 2016-10-19 501 /*
5feeca3c Geert Uytterhoeven 2016-10-19 502 * Legacy GPIO number, so request the GPIO here and
5feeca3c Geert Uytterhoeven 2016-10-19 503 * convert it to descriptor.
5feeca3c Geert Uytterhoeven 2016-10-19 504 */
5feeca3c Geert Uytterhoeven 2016-10-19 505 if (button->active_low)
5feeca3c Geert Uytterhoeven 2016-10-19 @506 flags |= GPIOF_ACTIVE_LOW;
bc8f1eaf Ben Dooks 2009-11-10 507
5feeca3c Geert Uytterhoeven 2016-10-19 508 error = devm_gpio_request_one(&pdev->dev, button->gpio, flags,
5feeca3c Geert Uytterhoeven 2016-10-19 509 desc);
:::::: The code at line 506 was first introduced by commit
:::::: 5feeca3c1e39c01f9ef5abc94dea94021ccf94fc Input: gpio_keys - add support for GPIO descriptors
:::::: TO: Geert Uytterhoeven <geert+renesas@glider.be>
:::::: CC: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
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: 27800 bytes --]
next prev parent reply other threads:[~2016-11-16 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:54 [PATCH -next] Input: gpio_keys: set input direction explicitly for gpio keys Sudeep Holla
2016-11-16 12:43 ` kbuild test robot
2016-11-16 12:48 ` kbuild test robot [this message]
2016-11-16 13:42 ` [PATCH v2 " Sudeep Holla
2016-11-16 17:36 ` Dmitry Torokhov
2016-11-16 17:42 ` Sudeep Holla
2016-11-16 18:34 ` Dmitry Torokhov
2016-11-16 18:39 ` Sudeep Holla
2016-11-16 18:38 ` [PATCH v3 " Sudeep Holla
2016-11-17 1:18 ` Dmitry Torokhov
2016-11-17 9:48 ` Sudeep Holla
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=201611162016.1LsBx0KB%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sudeep.holla@arm.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).