linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [linux-next:master 4773/10581] arch/arm/mach-prima2/pm.c:17:10: fatal error: linux/rtc/sirfsoc_rtciobrg.h: No such file or directory
Date: Sat, 13 Feb 2021 06:48:20 +0800	[thread overview]
Message-ID: <202102130609.nQGqL1WM-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   671176b0016c80b3943cb5387312c886aba3308d
commit: 9d0735519f99948c5b5c22426b682ced7f7af9be [4773/10581] rtc: remove sirfsoc driver
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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9d0735519f99948c5b5c22426b682ced7f7af9be
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 9d0735519f99948c5b5c22426b682ced7f7af9be
        # 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>

Note: the linux-next/master HEAD 671176b0016c80b3943cb5387312c886aba3308d builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

>> arch/arm/mach-prima2/pm.c:17:10: fatal error: linux/rtc/sirfsoc_rtciobrg.h: No such file or directory
      17 | #include <linux/rtc/sirfsoc_rtciobrg.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.
--
>> 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 +17 arch/arm/mach-prima2/pm.c

2558bd99cb1426 Rongjun Ying 2011-09-21 @17  #include <linux/rtc/sirfsoc_rtciobrg.h>
f81309067ff2d8 Russell King 2015-06-01  18  #include <asm/outercache.h>
2558bd99cb1426 Rongjun Ying 2011-09-21  19  #include <asm/suspend.h>
2558bd99cb1426 Rongjun Ying 2011-09-21  20  #include <asm/hardware/cache-l2x0.h>
2558bd99cb1426 Rongjun Ying 2011-09-21  21  

:::::: The code at line 17 was first introduced by commit
:::::: 2558bd99cb1426a05ac8f1c78dc9c75a83ceb4bb ARM: CSR: PM: add sleep entry for SiRFprimaII

:::::: TO: Rongjun Ying <rongjun.ying@csr.com>
:::::: CC: Barry Song <21cnbao@gmail.com>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 54176 bytes --]

                 reply	other threads:[~2021-02-12 22:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202102130609.nQGqL1WM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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