From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] rtc: remove sirfsoc driver
Date: Thu, 21 Jan 2021 12:26:29 +0800 [thread overview]
Message-ID: <202101211221.y93PufTi-lkp@intel.com> (raw)
In-Reply-To: <20210120154158.1860736-2-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
Hi Arnd,
I love your patch! Yet something to improve:
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on soc/for-next linux/master linus/master v5.11-rc4 next-20210120]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/rtc-remove-obsolete-drivers/20210120-235148
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/ffcefa0774c608b57d5ea429ad445201d2d2aea7
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Arnd-Bergmann/rtc-remove-obsolete-drivers/20210120-235148
git checkout ffcefa0774c608b57d5ea429ad445201d2d2aea7
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/input/misc/sirfsoc-onkey.c:14:10: fatal error: linux/rtc/sirfsoc_rtciobrg.h: No such file or directory
14 | #include <linux/rtc/sirfsoc_rtciobrg.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +14 drivers/input/misc/sirfsoc-onkey.c
9b5f953ddc3247dd Binghua Duan 2013-06-02 @14 #include <linux/rtc/sirfsoc_rtciobrg.h>
9b5f953ddc3247dd Binghua Duan 2013-06-02 15 #include <linux/of.h>
a1a7521064428fc1 Xianglong Du 2014-02-15 16 #include <linux/workqueue.h>
9b5f953ddc3247dd Binghua Duan 2013-06-02 17
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 54185 bytes --]
next prev parent reply other threads:[~2021-01-21 4:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:41 [PATCH 0/3] rtc: remove obsolete drivers Arnd Bergmann
2021-01-20 15:41 ` Arnd Bergmann
2021-01-20 15:41 ` [PATCH 1/3] rtc: remove sirfsoc driver Arnd Bergmann
2021-01-20 15:41 ` Arnd Bergmann
2021-01-20 20:36 ` kernel test robot
2021-01-20 21:02 ` Arnd Bergmann
2021-01-20 21:20 ` Barry Song
2021-01-20 21:20 ` Barry Song
2021-01-21 4:26 ` kernel test robot [this message]
2021-01-20 15:41 ` [PATCH 2/3] rtc: remove ste coh901 driver Arnd Bergmann
2021-01-20 15:41 ` Arnd Bergmann
2021-01-21 12:23 ` Linus Walleij
2021-01-21 12:23 ` Linus Walleij
2021-01-20 15:41 ` [PATCH 3/3] rtc: remove ste ab3100 driver Arnd Bergmann
2021-01-20 15:41 ` Arnd Bergmann
2021-01-21 12:23 ` Linus Walleij
2021-01-21 12:23 ` Linus Walleij
2021-01-23 13:57 ` [PATCH 0/3] rtc: remove obsolete drivers Alexandre Belloni
2021-01-23 13:57 ` Alexandre Belloni
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=202101211221.y93PufTi-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.