LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Oleksandr Shamray <oleksandrs@mellanox.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
openbmc@lists.ozlabs.org, joel@jms.id.au, jiri@resnulli.us,
tklauser@distanz.ch, linux-serial@vger.kernel.org,
system-sw-low-level@mellanox.com, robh+dt@kernel.org,
openocd-devel-owner@lists.sourceforge.net,
linux-api@vger.kernel.org, davem@davemloft.net,
mchehab@kernel.org, Oleksandr Shamray <oleksandrs@mellanox.com>
Subject: Re: [patch v22 1/4] drivers: jtag: Add JTAG core driver
Date: Tue, 29 May 2018 20:06:12 +0800 [thread overview]
Message-ID: <201805291924.tuUwoWI9%fengguang.wu@intel.com> (raw)
In-Reply-To: <1527508827-30724-2-git-send-email-oleksandrs@mellanox.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hi Oleksandr,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17-rc7]
[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/Oleksandr-Shamray/JTAG-driver-introduction/20180529-185749
config: i386-tinyconfig (attached as .config)
compiler: gcc-8 (Debian 8.1.0-3) 8.1.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> ./usr/include/linux/jtag.h:63: found __[us]{8,16,32,64} type without #include <linux/types.h>
---
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: 6306 bytes --]
next prev parent reply other threads:[~2018-05-29 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 12:00 [patch v22 0/4] JTAG driver introduction Oleksandr Shamray
2018-05-28 12:00 ` [patch v22 1/4] drivers: jtag: Add JTAG core driver Oleksandr Shamray
2018-05-29 12:06 ` kbuild test robot [this message]
2018-05-28 12:00 ` [patch v22 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver Oleksandr Shamray
2018-05-28 12:00 ` [patch v22 3/4] Documentation: jtag: Add bindings for " Oleksandr Shamray
2018-05-28 12:00 ` [patch v22 4/4] Documentation: jtag: Add ABI documentation Oleksandr Shamray
2018-05-28 20:32 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 10:34 [patch v22 0/4] JTAG driver introduction Oleksandr Shamray
2018-05-28 10:34 ` [patch v22 1/4] drivers: jtag: Add JTAG core driver Oleksandr Shamray
2018-05-28 12:35 ` Greg KH
2018-05-28 15:59 ` Oleksandr Shamray
2018-05-29 7:16 ` Greg KH
2018-05-29 20:08 ` kbuild test robot
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=201805291924.tuUwoWI9%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=joel@jms.id.au \
--cc=kbuild-all@01.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=oleksandrs@mellanox.com \
--cc=openbmc@lists.ozlabs.org \
--cc=openocd-devel-owner@lists.sourceforge.net \
--cc=robh+dt@kernel.org \
--cc=system-sw-low-level@mellanox.com \
--cc=tklauser@distanz.ch \
--subject='Re: [patch v22 1/4] drivers: jtag: Add JTAG core driver' \
/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
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).