From: kbuild test robot <lkp@intel.com>
To: Wei Xu <xuwei5@hisilicon.com>
Cc: kbuild-all@01.org, xuwei5@hisilicon.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linus.walleij@linaro.org,
rjw@rjwysocki.net, lenb@kernel.org,
mika.westerberg@linux.intel.com, andy.shevchenko@gmail.com,
linuxarm@huawei.com, shameerali.kolothum.thodi@huawei.com,
jonathan.cameron@huawei.com, john.garry@huawei.com,
salil.mehta@huawei.com, shiju.jose@huawei.com,
jinying@hisilicon.com, zhangyi.ac@huawei.com,
liguozhu@hisilicon.com, tangkunshan@huawei.com,
huangdaode@hisilicon.com
Subject: Re: [PATCH v2] gpio: pl061: Fix the issue failed to register the ACPI interrtupion
Date: Sun, 18 Aug 2019 20:58:22 +0800 [thread overview]
Message-ID: <201908182058.MCOd1cfR%lkp@intel.com> (raw)
In-Reply-To: <1565946336-20080-1-git-send-email-xuwei5@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
Hi Wei,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc4 next-20190816]
[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/Wei-Xu/gpio-pl061-Fix-the-issue-failed-to-register-the-ACPI-interrtupion/20190818-183921
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.0
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
GCC_VERSION=7.4.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/gpio/gpio-pl061.c:29:10: fatal error: gpiolib-acpi.h: No such file or directory
#include "gpiolib-acpi.h"
^~~~~~~~~~~~~~~~
compilation terminated.
vim +29 drivers/gpio/gpio-pl061.c
27
28 #include "gpiolib.h"
> 29 #include "gpiolib-acpi.h"
30
---
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: 71381 bytes --]
next prev parent reply other threads:[~2019-08-18 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 9:05 [PATCH v2] gpio: pl061: Fix the issue failed to register the ACPI interrtupion Wei Xu
2019-08-16 13:40 ` Andy Shevchenko
2019-08-19 12:59 ` Wei Xu
2019-08-18 12:58 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-16 8:58 Wei Xu
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=201908182058.MCOd1cfR%lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=huangdaode@hisilicon.com \
--cc=jinying@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=liguozhu@hisilicon.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=salil.mehta@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tangkunshan@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangyi.ac@huawei.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;
as well as URLs for NNTP newsgroup(s).