From: Nam Cao <namcao@linutronix.de>
To: Vivian Wang <wangruikang@iscas.ac.cn>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: Inochi Amaoto <inochiama@gmail.com>,
linux-kernel@vger.kernel.org,
Vivian Wang <wangruikang@iscas.ac.cn>,
Han Gao <rabenda.cn@gmail.com>,
linux-riscv@lists.infradead.org, Yao Zi <ziyao@disroot.org>
Subject: Re: [PATCH 0/2] riscv: tests: Make RISCV_KPROBES_KUNIT tristate
Date: Tue, 21 Oct 2025 12:36:05 +0200 [thread overview]
Message-ID: <87sefc1qzu.fsf@yellow.woof> (raw)
In-Reply-To: <20251020-riscv-kunit-kconfig-fix-6-18-v1-0-d773b5d5ce48@iscas.ac.cn>
Vivian Wang <wangruikang@iscas.ac.cn> writes:
> Fix an allmodconfig warning on v6.18-rc1:
>
> WARNING: 3 bad relocations
> ffffffff81e24118 R_RISCV_64 kunit_unary_assert_format
> ffffffff81e24a60 R_RISCV_64 kunit_binary_assert_format
> ffffffff81e269d0 R_RISCV_JUMP_SLOT __kunit_do_failed_assertion
>
> While we're at it, rename the test to remove the word "test", in order
> to conform to the style guide.
Reviewed-by: Nam Cao <namcao@linutronix.de>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Vivian Wang <wangruikang@iscas.ac.cn>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Han Gao <rabenda.cn@gmail.com>, Icenowy Zheng <uwu@icenowy.me>,
Inochi Amaoto <inochiama@gmail.com>, Yao Zi <ziyao@disroot.org>,
Vivian Wang <wangruikang@iscas.ac.cn>
Subject: Re: [PATCH 0/2] riscv: tests: Make RISCV_KPROBES_KUNIT tristate
Date: Tue, 21 Oct 2025 12:36:05 +0200 [thread overview]
Message-ID: <87sefc1qzu.fsf@yellow.woof> (raw)
In-Reply-To: <20251020-riscv-kunit-kconfig-fix-6-18-v1-0-d773b5d5ce48@iscas.ac.cn>
Vivian Wang <wangruikang@iscas.ac.cn> writes:
> Fix an allmodconfig warning on v6.18-rc1:
>
> WARNING: 3 bad relocations
> ffffffff81e24118 R_RISCV_64 kunit_unary_assert_format
> ffffffff81e24a60 R_RISCV_64 kunit_binary_assert_format
> ffffffff81e269d0 R_RISCV_JUMP_SLOT __kunit_do_failed_assertion
>
> While we're at it, rename the test to remove the word "test", in order
> to conform to the style guide.
Reviewed-by: Nam Cao <namcao@linutronix.de>
next prev parent reply other threads:[~2025-10-21 10:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 12:23 [PATCH 0/2] riscv: tests: Make RISCV_KPROBES_KUNIT tristate Vivian Wang
2025-10-20 12:23 ` Vivian Wang
2025-10-20 12:23 ` [PATCH 1/2] riscv: tests: Rename kprobes_test_riscv to kprobes_riscv Vivian Wang
2025-10-20 12:23 ` Vivian Wang
2025-10-20 12:23 ` [PATCH 2/2] riscv: tests: Make RISCV_KPROBES_KUNIT tristate Vivian Wang
2025-10-20 12:23 ` Vivian Wang
2025-10-20 12:59 ` [PATCH 0/2] " Vivian Wang
2025-10-20 12:59 ` Vivian Wang
2025-10-21 10:36 ` Nam Cao [this message]
2025-10-21 10:36 ` Nam Cao
2025-10-22 0:47 ` Inochi Amaoto
2025-10-22 0:47 ` Inochi Amaoto
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=87sefc1qzu.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=inochiama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=wangruikang@iscas.ac.cn \
--cc=ziyao@disroot.org \
/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.