From: kbuild test robot <lkp@intel.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: kbuild-all@01.org, linux-usb@vger.kernel.org,
linux-spi@vger.kernel.org, linux-fpga@vger.kernel.org,
gregkh@linuxfoundation.org, broonie@kernel.org, atull@kernel.org,
mdf@kernel.org
Subject: [2/3] spi: add FTDI MPSSE SPI controller driver
Date: Tue, 6 Nov 2018 14:29:16 +0800 [thread overview]
Message-ID: <201811061417.c8hGmD4G%fengguang.wu@intel.com> (raw)
Hi Anatolij,
I love your patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.20-rc1 next-20181105]
[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/Anatolij-Gustschin/Add-support-for-ARRI-FPGA-configuration/20181106-090458
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> drivers//spi/spi-ftdi-mpsse.c:27:2: error: expected identifier before numeric constant
CS = BIT(3),
^~
vim +27 drivers//spi/spi-ftdi-mpsse.c
22
23 enum gpiol {
24 SK = BIT(0),
25 DO = BIT(1),
26 DI = BIT(2),
> 27 CS = BIT(3),
28 };
29
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2018-11-06 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 6:29 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-06 9:58 [2/3] spi: add FTDI MPSSE SPI controller driver Anatolij Gustschin
2018-11-06 5:07 kbuild test robot
2018-11-05 16:19 Anatolij Gustschin
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=201811061417.c8hGmD4G%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=agust@denx.de \
--cc=atull@kernel.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdf@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