From: Charlie Jenkins <charlie@rivosinc.com>
To: Yong-Xuan Wang <yongxuan.wang@sifive.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kselftest@vger.kernel.org, greentime.hu@sifive.com,
vincent.chen@sifive.com, andybnac@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH 0/2] selftest: fix riscv/vector tests
Date: Thu, 9 Jan 2025 16:27:33 -0800 [thread overview]
Message-ID: <Z4BpdQA4t1ip0yK7@ghost> (raw)
In-Reply-To: <20241220091730.28006-1-yongxuan.wang@sifive.com>
On Fri, Dec 20, 2024 at 05:17:25PM +0800, Yong-Xuan Wang wrote:
> Add test counts and pass message to remove warning of riscv/vector tests.
A similar patch has been staged on Palmers for-next tree that I sent out
a long time ago. I also reworked these tests so that they use the
kselftest_harness [1].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git/commit/?h=for-next&id=8fcaf922831887e32c8bdf5ebff76bbd80c971cb
- Charlie
>
> Yong-Xuan Wang (2):
> tools: selftests: riscv: Add pass message for v_initval_nolibc
> tools: selftests: riscv: Add test count for vstate_prctl
>
> tools/testing/selftests/riscv/vector/v_initval_nolibc.c | 4 ++++
> tools/testing/selftests/riscv/vector/vstate_prctl.c | 2 ++
> 2 files changed, 6 insertions(+)
>
> --
> 2.17.1
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-01-10 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 9:17 [PATCH 0/2] selftest: fix riscv/vector tests Yong-Xuan Wang
2024-12-20 9:17 ` [PATCH 1/2] tools: selftests: riscv: Add pass message for v_initval_nolibc Yong-Xuan Wang
2024-12-20 9:17 ` [PATCH 2/2] tools: selftests: riscv: Add test count for vstate_prctl Yong-Xuan Wang
2024-12-20 15:29 ` [PATCH 0/2] selftest: fix riscv/vector tests Andrew Jones
2025-01-05 16:25 ` Andy Chiu
2025-01-09 19:40 ` patchwork-bot+linux-riscv
2025-01-10 0:27 ` Charlie Jenkins [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=Z4BpdQA4t1ip0yK7@ghost \
--to=charlie@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.com \
--cc=yongxuan.wang@sifive.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