From: kernel test robot <lkp@intel.com>
To: Vitaly Wool <vitaly.wool@konsulko.com>, linux-riscv@lists.infradead.org
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Bin Meng <bin.meng@windriver.com>,
Anup Patel <anup@brainfault.org>,
Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Nicolas Pitre <nico@fluxnic.net>,
Vitaly Wool <vitaly.wool@konsulko.com>
Subject: Re: [PATCH v4] RISC-V: enable XIP
Date: Sun, 7 Mar 2021 17:40:03 +0800 [thread overview]
Message-ID: <202103071709.5wob3Unh-lkp@intel.com> (raw)
In-Reply-To: <20210306121438.12827-1-vitaly.wool@konsulko.com>
[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]
Hi Vitaly,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.12-rc2 next-20210305]
[cannot apply to linux/master]
[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/Vitaly-Wool/RISC-V-enable-XIP/20210307-103904
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 280d542f6ffac0e6d65dc267f92191d509b13b64
config: riscv-defconfig (attached as .config)
compiler: riscv64-linux-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/c9cb15092dcf53140fba57780677a9dcaef70612
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Vitaly-Wool/RISC-V-enable-XIP/20210307-103904
git checkout c9cb15092dcf53140fba57780677a9dcaef70612
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
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 >>):
arch/riscv/kernel/cpu_ops_sbi.c: In function 'get_secondary_start_phys':
>> arch/riscv/kernel/cpu_ops_sbi.c:59:3: error: implicit declaration of function 'XIP_PHYS_ADDR' [-Werror=implicit-function-declaration]
59 | XIP_PHYS_ADDR(secondary_start_sbi) :
| ^~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/XIP_PHYS_ADDR +59 arch/riscv/kernel/cpu_ops_sbi.c
55
56 static inline unsigned long get_secondary_start_phys(void)
57 {
58 return IS_ENABLED(CONFIG_XIP_KERNEL) ?
> 59 XIP_PHYS_ADDR(secondary_start_sbi) :
60 __pa_symbol(secondary_start_sbi);
61 }
62
---
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: 21443 bytes --]
next prev parent reply other threads:[~2021-03-07 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 12:14 [PATCH v4] RISC-V: enable XIP Vitaly Wool
2021-03-07 9:40 ` kernel test robot [this message]
2021-03-08 3:58 ` kernel test robot
2021-03-21 20:21 ` Guenter Roeck
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=202103071709.5wob3Unh-lkp@intel.com \
--to=lkp@intel.com \
--cc=alistair.francis@wdc.com \
--cc=anup@brainfault.org \
--cc=bin.meng@windriver.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nico@fluxnic.net \
--cc=palmerdabbelt@google.com \
--cc=vitaly.wool@konsulko.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