From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [linux-next:master 8520/9515] arch/arm/mach-pxa/cm-x300.c:26:10: fatal error: linux/platform_data/rtc-v3020.h: No such file or directory
Date: Wed, 1 Feb 2023 09:37:45 +0800 [thread overview]
Message-ID: <202302010907.ldMaJ10q-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 80bd9028fecadae4e8e3a278cd32d74badc2a6e0
commit: bf5c08d3de21fc9145b829f668c71fa346bb8644 [8520/9515] rtc: remove v3020 driver
config: arm-cm_x300_defconfig (https://download.01.org/0day-ci/archive/20230201/202302010907.ldMaJ10q-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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=bf5c08d3de21fc9145b829f668c71fa346bb8644
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 bf5c08d3de21fc9145b829f668c71fa346bb8644
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 80bd9028fecadae4e8e3a278cd32d74badc2a6e0 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> arch/arm/mach-pxa/cm-x300.c:26:10: fatal error: linux/platform_data/rtc-v3020.h: No such file or directory
26 | #include <linux/platform_data/rtc-v3020.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +26 arch/arm/mach-pxa/cm-x300.c
cf75d8d213f58c0 Mike Rapoport 2008-08-26 21
cf75d8d213f58c0 Mike Rapoport 2008-08-26 22 #include <linux/gpio.h>
9b00bc7b901ff67 Linus Walleij 2018-02-12 23 #include <linux/gpio/machine.h>
cf75d8d213f58c0 Mike Rapoport 2008-08-26 24 #include <linux/dm9000.h>
cf75d8d213f58c0 Mike Rapoport 2008-08-26 25 #include <linux/leds.h>
cd9b518b98d3e98 Alexandre Belloni 2016-06-27 @26 #include <linux/platform_data/rtc-v3020.h>
783bc78836563af Thierry Reding 2015-10-05 27 #include <linux/pwm.h>
db205463fd24c09 Igor Grinberg 2009-11-10 28 #include <linux/pwm_backlight.h>
cf75d8d213f58c0 Mike Rapoport 2008-08-26 29
:::::: The code at line 26 was first introduced by commit
:::::: cd9b518b98d3e989f523e63b2ffda78467a3679e rtc: v3020: move rtc-v3020.h to platform_data
:::::: TO: Alexandre Belloni <alexandre.belloni@free-electrons.com>
:::::: CC: Alexandre Belloni <alexandre.belloni@free-electrons.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-01 1:38 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=202302010907.ldMaJ10q-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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