From: kbuild test robot <lkp@intel.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrey Smirnov <andrew.smirnov@gmail.com>,
linux-watchdog@vger.kernel.org, cphealy@gmail.com,
Lucas Stach <l.stach@pengutronix.de>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
Lee Jones <lee.jones@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavel Machek <pavel@ucw.cz>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Johan Hovold <johan@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Subject: Re: [PATCH v11 4/5] watchdog: Add RAVE SP watchdog driver
Date: Thu, 9 Nov 2017 06:45:17 +0800 [thread overview]
Message-ID: <201711090649.vSevbVsX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171106152935.16920-5-andrew.smirnov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi Andrey,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc8]
[cannot apply to next-20171108]
[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/Andrey-Smirnov/ZII-RAVE-platform-driver/20171109-033941
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm64
All errors (new ones prefixed by >>):
>> drivers//watchdog/rave-sp-wdt.c:28:27: fatal error: linux/rave-sp.h: No such file or directory
#include <linux/rave-sp.h>
^
compilation terminated.
vim +28 drivers//watchdog/rave-sp-wdt.c
> 28 #include <linux/rave-sp.h>
29 #include <linux/reboot.h>
30 #include <linux/slab.h>
31 #include <linux/watchdog.h>
32
---
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: 57539 bytes --]
next prev parent reply other threads:[~2017-11-08 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 15:29 [PATCH v11 0/5] ZII RAVE platform driver Andrey Smirnov
2017-11-06 15:29 ` [PATCH v11 1/5] serdev: Make .remove in struct serdev_device_driver optional Andrey Smirnov
2017-11-06 15:29 ` [PATCH v11 2/5] serdev: Introduce devm_serdev_device_open() Andrey Smirnov
2017-11-06 15:29 ` [PATCH v11 3/5] mfd: Add driver for RAVE Supervisory Processor Andrey Smirnov
2017-11-08 22:09 ` kbuild test robot
2017-11-06 15:29 ` [PATCH v11 4/5] watchdog: Add RAVE SP watchdog driver Andrey Smirnov
2017-11-08 22:45 ` kbuild test robot [this message]
2017-11-06 15:29 ` [PATCH v11 5/5] dt-bindings: watchdog: Add bindings for " Andrey Smirnov
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=201711090649.vSevbVsX%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andrew.smirnov@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=cphealy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=l.stach@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nikita.yoush@cogentembedded.com \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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®