From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Clinux=40weissschuh=2Enet=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, w@1wt.eu, shuah@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, falcon@tinylab.org
Subject: Re: [PATCH 0/6] selftests/nolibc: wire up riscv32
Date: Mon, 03 Feb 2025 19:15:48 +0000 [thread overview]
Message-ID: <173861014802.3409359.16765792882817041253.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241221-nolibc-rv32-v1-0-d9ef6dab7c63@weissschuh.net>
Hello:
This series was applied to riscv/linux.git (fixes)
by Thomas Weißschuh <linux@weissschuh.net>:
On Sat, 21 Dec 2024 15:44:27 +0100 you wrote:
> Nolibc has support for riscv32. But the testsuite did not allow to test
> it so far. Add a test configuration.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (6):
> tools/nolibc: add support for waitid()
> selftests/nolibc: use waitid() over waitpid()
> selftests/nolibc: use a pipe to in vfprintf tests
> selftests/nolibc: skip tests for unimplemented syscalls
> selftests/nolibc: rename riscv to riscv64
> selftests/nolibc: add configurations for riscv32
>
> [...]
Here is the summary with links:
- [1/6] tools/nolibc: add support for waitid()
https://git.kernel.org/riscv/c/7f89bc51101c
- [2/6] selftests/nolibc: use waitid() over waitpid()
https://git.kernel.org/riscv/c/a0bc8947ac73
- [3/6] selftests/nolibc: use a pipe to in vfprintf tests
https://git.kernel.org/riscv/c/4c7f09ab79b1
- [4/6] selftests/nolibc: skip tests for unimplemented syscalls
https://git.kernel.org/riscv/c/349afc8a52f8
- [5/6] selftests/nolibc: rename riscv to riscv64
https://git.kernel.org/riscv/c/a47b4b9fbaa1
- [6/6] selftests/nolibc: add configurations for riscv32
https://git.kernel.org/riscv/c/60fe18237f72
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 14:44 [PATCH 0/6] selftests/nolibc: wire up riscv32 Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 1/6] tools/nolibc: add support for waitid() Thomas Weißschuh
2024-12-21 16:35 ` Willy Tarreau
2024-12-22 11:39 ` Thomas Weißschuh
2024-12-23 8:13 ` Willy Tarreau
2024-12-21 14:44 ` [PATCH 2/6] selftests/nolibc: use waitid() over waitpid() Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 3/6] selftests/nolibc: use a pipe to in vfprintf tests Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 4/6] selftests/nolibc: skip tests for unimplemented syscalls Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 5/6] selftests/nolibc: rename riscv to riscv64 Thomas Weißschuh
2025-01-17 19:13 ` Charlie Jenkins
2024-12-21 14:44 ` [PATCH 6/6] selftests/nolibc: add configurations for riscv32 Thomas Weißschuh
2025-01-17 19:10 ` Charlie Jenkins
2025-02-03 19:15 ` patchwork-bot+linux-riscv [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=173861014802.3409359.16765792882817041253.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Clinux=40weissschuh=2Enet=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=aou@eecs.berkeley.edu \
--cc=falcon@tinylab.org \
--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=shuah@kernel.org \
--cc=w@1wt.eu \
/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