From: kbuild test robot <lkp@intel.com>
To: AZO <typesylph@gmail.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
typesylph@gmail.com
Subject: Re: [PATCH] drivers: input: joystick: Add PSX (Play Station 1/2) pad with SPI driver.
Date: Wed, 26 Apr 2017 06:24:05 +0800 [thread overview]
Message-ID: <201704260607.2xZFs7pU%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170425074159.8533-1-typesylph@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Hi AZO,
[auto build test ERROR on input/next]
[also build test ERROR on v4.11-rc8 next-20170424]
[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/AZO/drivers-input-joystick-Add-PSX-Play-Station-1-2-pad-with-SPI-driver/20170425-182329
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: i386-allmodconfig (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 >>):
>> make[4]: *** No rule to make target 'drivers/input/joystick/rpisense-js.c', needed by 'drivers/input/joystick/rpisense-js.o'.
make[4]: Target '__build' not remade because of errors.
---
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: 58986 bytes --]
next prev parent reply other threads:[~2017-04-25 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 7:41 AZO
2017-04-25 22:16 ` kbuild test robot
2017-04-25 22:24 ` kbuild test robot [this message]
2017-04-25 23:07 ` AZO
2017-04-25 14:44 AZO
2017-04-26 8:52 ` Antonio Ospite
2017-04-26 11:46 ` AZO
2017-04-27 8:17 ` Dmitry Torokhov
2017-04-28 2:38 Tomohiro Yoshidomi
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=201704260607.2xZFs7pU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=typesylph@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®