From: Palmer Dabbelt <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected],
Conor Dooley <[email protected]>,
[email protected]
Subject: Re: [ammarfaizi2-block:palmer/linux/for-next 46/47] cpufeature.c:undefined reference to `riscv_cbom_block_size'
Date: Fri, 09 Dec 2022 20:14:42 -0800 (PST) [thread overview]
Message-ID: <mhng-79a0534e-a244-42b0-b313-0ab7cc3709c9@palmer-ri-x1c9> (raw)
In-Reply-To: <[email protected]>
On Fri, 09 Dec 2022 18:56:27 PST (-0800), [email protected] wrote:
> tree: https://github.com/ammarfaizi2/linux-block palmer/linux/for-next
> head: 4f32e3ab94b6d98de7ffb7a781df3c06c8dcd166
> commit: 68dc0718407d8e9c84c530df5298078a57a8000a [46/47] RISC-V: Ensure Zicbom has a valid block size
> config: riscv-randconfig-r042-20221209
> compiler: riscv64-linux-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://github.com/ammarfaizi2/linux-block/commit/68dc0718407d8e9c84c530df5298078a57a8000a
> git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
> git fetch --no-tags ammarfaizi2-block palmer/linux/for-next
> git checkout 68dc0718407d8e9c84c530df5298078a57a8000a
> # 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=riscv SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <[email protected]>
>
> All errors (new ones prefixed by >>):
>
> riscv64-linux-ld: arch/riscv/kernel/cpufeature.o: in function `.L0 ':
>>> cpufeature.c:(.text.unlikely+0x1a): undefined reference to `riscv_cbom_block_size'
I forgot to base this on 5c20a3a9df19 ("RISC-V: Fix compilation without
RISCV_ISA_ZICBOM"), which I keep forgetting about because it went in
without an Ack (which has made through a bunch of headaches).
I'm rewriting my for-next since this was merged pretty recently, so with
any luck I got that right. It's on for-next now.
prev parent reply other threads:[~2022-12-10 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 2:56 [ammarfaizi2-block:palmer/linux/for-next 46/47] cpufeature.c:undefined reference to `riscv_cbom_block_size' kernel test robot
2022-12-10 4:14 ` Palmer Dabbelt [this message]
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=mhng-79a0534e-a244-42b0-b313-0ab7cc3709c9@palmer-ri-x1c9 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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