From: kbuild test robot <lkp@intel.com>
To: Cameron Gutman <aicommander@gmail.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com, rojtberg@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Cameron Gutman <aicommander@gmail.com>
Subject: Re: [PATCH 4/5] Input: xpad - restore LED state after device resume
Date: Sun, 5 Feb 2017 09:17:14 +0800 [thread overview]
Message-ID: <201702050949.mTJDZN2o%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170205003002.28160-5-aicommander@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Hi Cameron,
[auto build test ERROR on input/next]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Cameron-Gutman/Correctly-support-some-quirky-Xbox-One-pads/20170205-083659
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: x86_64-randconfig-x016-201706 (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/joystick/xpad.c: In function 'xpad_resume':
>> drivers/input/joystick/xpad.c:1700:10: error: 'struct usb_xpad' has no member named 'led'
if (xpad->led)
^~
>> drivers/input/joystick/xpad.c:1701:3: error: implicit declaration of function 'xpad_send_led_command' [-Werror=implicit-function-declaration]
xpad_send_led_command(xpad, xpad->led->led_cdev.brightness);
^~~~~~~~~~~~~~~~~~~~~
drivers/input/joystick/xpad.c:1701:35: error: 'struct usb_xpad' has no member named 'led'
xpad_send_led_command(xpad, xpad->led->led_cdev.brightness);
^~
cc1: some warnings being treated as errors
vim +1700 drivers/input/joystick/xpad.c
1694 retval = xpad_start_xbox_one(xpad);
1695 }
1696 mutex_unlock(&input->mutex);
1697 }
1698
1699 /* LED state is lost across resume, so resend the last command */
> 1700 if (xpad->led)
> 1701 xpad_send_led_command(xpad, xpad->led->led_cdev.brightness);
1702
1703 return retval;
1704 }
---
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: 27535 bytes --]
next prev parent reply other threads:[~2017-02-05 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 0:29 [PATCH 0/5] Correctly support some quirky Xbox One pads Cameron Gutman
2017-02-05 0:29 ` [PATCH 1/5] Input: xpad - use a packet array to start " Cameron Gutman
2017-02-05 0:29 ` [PATCH 2/5] Input: xpad - add init packet for Hori and Titanfall 2 pads Cameron Gutman
2017-02-05 0:30 ` [PATCH 3/5] Input: xpad - send rumble on Xbox One init to fix PowerA pads Cameron Gutman
2017-02-06 22:13 ` Dmitry Torokhov
2017-02-05 0:30 ` [PATCH 4/5] Input: xpad - restore LED state after device resume Cameron Gutman
2017-02-05 1:17 ` kbuild test robot [this message]
2017-02-05 1:47 ` Cameron Gutman
2017-02-06 22:05 ` Dmitry Torokhov
2017-02-06 22:57 ` Cameron Gutman
2017-02-05 0:30 ` [PATCH 5/5] Input: xpad - fix stuck mode button on Xbox One S pad Cameron Gutman
2017-02-06 22:03 ` Dmitry Torokhov
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=201702050949.mTJDZN2o%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aicommander@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rojtberg@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
all inboxes | Powered by JetHome®