From: Charlie Jenkins via B4 Relay <devnull+thecharlesjenkins.gmail.com@kernel.org>
To: Shuah Khan <shuah@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
Andy Chiu <andybnac@gmail.com>,
Deepak Gupta <debug@rivosinc.com>
Cc: linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Charlie Jenkins <thecharlesjenkins@gmail.com>
Subject: [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi
Date: Mon, 09 Mar 2026 18:52:09 -0700 [thread overview]
Message-ID: <20260309-fix_selftests-v2-0-9d5a553a531e@gmail.com> (raw)
There are a couple of compilation issues of the riscv selftests.
Coincidentally two of the issues are independent problems with not
including the header that includes the BIT() macro and the other issue
is from checkpatch incorrectly suggesting to remove non-redundant
braces.
Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
---
Changes in v2:
- Fix compilation issue reported by kernel test bot and Sergey
- Link to v1: https://lore.kernel.org/r/20260305-fix_selftests-v1-0-61b62d23500b@gmail.com
---
Charlie Jenkins (4):
selftests: riscv: Add definition of BIT() macro
selftests: riscv: Add braces around EXPECT_EQ()
riscv: ptrace: Fix BIT() compilation issues
selftests: riscv: Add license to cfi selftest
arch/riscv/include/uapi/asm/ptrace.h | 1 +
tools/testing/selftests/riscv/cfi/Makefile | 2 ++
tools/testing/selftests/riscv/vector/Makefile | 7 +++++--
tools/testing/selftests/riscv/vector/validate_v_ptrace.c | 16 ++++++++++------
4 files changed, 18 insertions(+), 8 deletions(-)
---
base-commit: c107785c7e8dbabd1c18301a1c362544b5786282
change-id: ${change-id}
- Charlie
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2026-03-10 1:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 1:52 Charlie Jenkins via B4 Relay [this message]
2026-03-10 1:52 ` [PATCH v2 1/4] selftests: riscv: Add definition of BIT() macro Charlie Jenkins via B4 Relay
2026-03-10 8:18 ` Sergey Matyukevich
2026-03-21 0:48 ` Paul Walmsley
2026-03-21 0:53 ` Paul Walmsley
2026-03-10 1:52 ` [PATCH v2 2/4] selftests: riscv: Add braces around EXPECT_EQ() Charlie Jenkins via B4 Relay
2026-03-10 3:50 ` Joe Perches
2026-03-10 8:17 ` Sergey Matyukevich
2026-03-21 0:24 ` Paul Walmsley
2026-04-03 17:46 ` Paul Walmsley
2026-03-10 1:52 ` [PATCH v2 3/4] riscv: ptrace: Fix BIT() compilation issues Charlie Jenkins via B4 Relay
2026-03-10 2:58 ` Deepak Gupta
2026-03-21 0:53 ` Paul Walmsley
2026-03-10 1:52 ` [PATCH v2 4/4] selftests: riscv: Add license to cfi selftest Charlie Jenkins via B4 Relay
2026-03-10 2:58 ` Deepak Gupta
2026-03-21 0:54 ` Paul Walmsley
2026-03-21 5:20 ` [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi patchwork-bot+linux-riscv
2026-04-03 18:30 ` patchwork-bot+linux-riscv
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=20260309-fix_selftests-v2-0-9d5a553a531e@gmail.com \
--to=devnull+thecharlesjenkins.gmail.com@kernel.org \
--cc=andybnac@gmail.com \
--cc=debug@rivosinc.com \
--cc=geomatsi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=shuah@kernel.org \
--cc=thecharlesjenkins@gmail.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