From: kbuild test robot <lkp@intel.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: kbuild-all@01.org, Jiri Kosina <jikos@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: i2c-hid: retrieve the GPIO parameters only when unset
Date: Mon, 21 Nov 2016 21:28:39 +0800 [thread overview]
Message-ID: <201611212149.WUepEXDV%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479729016-32307-1-git-send-email-benjamin.tissoires@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
Hi Benjamin,
[auto build test ERROR on hid/for-next]
[also build test ERROR on next-20161117]
[cannot apply to v4.9-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/Benjamin-Tissoires/HID-i2c-hid-retrieve-the-GPIO-parameters-only-when-unset/20161121-195550
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
drivers/hid/i2c-hid/i2c-hid.c: In function 'i2c_hid_init_irq':
>> drivers/hid/i2c-hid/i2c-hid.c:866:7: error: implicit declaration of function 'irq_get_trigger_type' [-Werror=implicit-function-declaration]
if (!irq_get_trigger_type(client->irq))
^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/irq_get_trigger_type +866 drivers/hid/i2c-hid/i2c-hid.c
860 struct i2c_hid *ihid = i2c_get_clientdata(client);
861 unsigned long irqflags = 0;
862 int ret;
863
864 dev_dbg(&client->dev, "Requesting IRQ: %d\n", client->irq);
865
> 866 if (!irq_get_trigger_type(client->irq))
867 irqflags = IRQF_TRIGGER_LOW;
868
869 ret = request_threaded_irq(client->irq, NULL, i2c_hid_irq,
---
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: 59453 bytes --]
prev parent reply other threads:[~2016-11-21 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 11:50 Benjamin Tissoires
2016-11-21 13:28 ` 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=201611212149.WUepEXDV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®