From: patchwork-bot+linux-riscv@kernel.org
To: Hui Wang <hui.wang@canonical.com>
Cc: linux-riscv@lists.infradead.org, mathieu.desnoyers@efficios.com,
peterz@infradead.org, shuah@kernel.org, paulmck@kernel.org,
boqun@kernel.org, zhouquan@iscas.ac.cn, ajones@ventanamicro.com,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] selftests/rseq: Fix a building error for riscv arch
Date: Wed, 08 Jul 2026 17:00:04 +0000 [thread overview]
Message-ID: <178353000492.3027451.2869777955092824432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707082348.36896-1-hui.wang@canonical.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Tue, 7 Jul 2026 16:23:48 +0800 you wrote:
> RISC-V rseq selftests include asm/fence.h from tools/arch/riscv,
> but the rseq Makefile only adds tools/include in the CFLAGS, this
> results in the building failure both for native and cross build:
>
> In file included from rseq.h:131,
> from rseq.c:37:
> rseq-riscv.h:11:10: fatal error: asm/fence.h: No such file or directory
>
> [...]
Here is the summary with links:
- [v2] selftests/rseq: Fix a building error for riscv arch
https://git.kernel.org/riscv/c/a2ac823d8a22
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-08 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:23 [PATCH v2] selftests/rseq: Fix a building error for riscv arch Hui Wang
2026-07-08 17:00 ` patchwork-bot+linux-riscv [this message]
2026-07-08 23:05 ` Paul Walmsley
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=178353000492.3027451.2869777955092824432.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=boqun@kernel.org \
--cc=hui.wang@canonical.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhouquan@iscas.ac.cn \
/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