From: kernel test robot <lkp@intel.com>
To: Himanshu Chauhan <hchauhan@ventanamicro.com>
Cc: oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_raid6_rvv_v5 65/68] include/linux/riscv_sse.h:11:10: fatal error: asm/sbi.h: No such file or directory
Date: Thu, 22 May 2025 05:53:37 +0800 [thread overview]
Message-ID: <202505220500.neuhfBvt-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_raid6_rvv_v5
head: 9b85cdf2ad159e2a8ee78d62c6b423942917119e
commit: d133a9e6c5f12d062db24a320a92a3d6aaacbc00 [65/68] riscv: Introduce HEST SSE notification handlers
config: i386-buildonly-randconfig-2002-20250521 (https://download.01.org/0day-ci/archive/20250522/202505220500.neuhfBvt-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250522/202505220500.neuhfBvt-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505220500.neuhfBvt-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/acpi/apei/ghes.c:20:
>> include/linux/riscv_sse.h:11:10: fatal error: asm/sbi.h: No such file or directory
11 | #include <asm/sbi.h>
| ^~~~~~~~~~~
compilation terminated.
vim +11 include/linux/riscv_sse.h
aa1594867bd2a5 Clément Léger 2024-12-06 8
aa1594867bd2a5 Clément Léger 2024-12-06 9 #include <linux/types.h>
aa1594867bd2a5 Clément Léger 2024-12-06 10 #include <linux/linkage.h>
1cbb58375d3584 Andrew Jones 2025-03-19 @11 #include <asm/sbi.h>
aa1594867bd2a5 Clément Léger 2024-12-06 12
:::::: The code at line 11 was first introduced by commit
:::::: 1cbb58375d3584633396096f9eded7943919f8cf riscv: Fix arch_sse_init_event
:::::: TO: Andrew Jones <ajones@ventanamicro.com>
:::::: CC: Anup Patel <anup@brainfault.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-21 21:53 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=202505220500.neuhfBvt-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=hchauhan@ventanamicro.com \
--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 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.