From: Paul Walmsley <pjw@kernel.org>
To: patchwork-bot+linux-riscv@kernel.org
Cc: Andy Chiu <tchiu@tenstorrent.com>,
linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
andybnac@gmail.com, dfustini@oss.tenstorrent.com,
greentime.hu@sifive.com, linux-kernel@vger.kernel.org,
olof@lixom.net
Subject: Re: [PATCH v6 0/8] riscv: optimize mode switch latency for Vector
Date: Wed, 7 Oct 2026 08:20:18 -0600 (MDT) [thread overview]
Message-ID: <cce463c9-3a77-d21c-56e7-5eaa0a290f14@kernel.org> (raw)
In-Reply-To: <179127960878.2107992.9155163918962890142.git-patchwork-notify@kernel.org>
On Tue, 6 Oct 2026, patchwork-bot+linux-riscv@kernel.org wrote:
> Hello:
>
> This series was applied to riscv/linux.git (for-next)
> by Paul Walmsley <pjw@kernel.org>:
>
[ ... ]
> Here is the summary with links:
> - [v6,1/8] riscv: do not read csr in vector context switch
> https://git.kernel.org/riscv/c/5fd018c630e2
> - [v6,2/8] riscv: vector: refactor context switch for kernel-mode vector
> https://git.kernel.org/riscv/c/4740b934ebe7
> - [v6,3/8] selftest: riscv: test vectorized user copy
> https://git.kernel.org/riscv/c/52318cf0fa6e
> - [v6,4/8] riscv: vector: refactor vector context operations
> https://git.kernel.org/riscv/c/1a5c75ee3d09
> - [v6,5/8] riscv: clarify vector state semantics on syscall and context switch
> https://git.kernel.org/riscv/c/cc12e55016ba
> - [v6,6/8] riscv: vector: adjust ptrace and signal behavior for INITIAL state
> https://git.kernel.org/riscv/c/0d4b43a7734d
> - [v6,7/8] selftests: riscv: Extend vector tests for sigreturn and ptrace
> https://git.kernel.org/riscv/c/6740ec489dd7
> - [v6,8/8] riscv: vector: optimize vstate operations
> (no matching commit)
Just to clarify, I only applied the first three patches, for the reason
mentioned earlier.
- Paul
next prev parent reply other threads:[~2026-10-07 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:51 Andy Chiu
2026-10-06 9:40 ` patchwork-bot+linux-riscv
2026-10-07 14:20 ` Paul Walmsley [this message]
2026-10-06 10:01 ` 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=cce463c9-3a77-d21c-56e7-5eaa0a290f14@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=dfustini@oss.tenstorrent.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=patchwork-bot+linux-riscv@kernel.org \
--cc=tchiu@tenstorrent.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
all inboxes | Powered by JetHome®