From: Paul Walmsley <pjw@kernel.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Andrew Jones <andrew.jones@oss.qualcomm.com>,
Jingwei Wang <wangjingwei@iscas.ac.cn>,
Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Revert "riscv: hwprobe: Fix stale vDSO data for late-initialized keys at boot"
Date: Wed, 29 Jul 2026 13:32:08 -0600 (MDT) [thread overview]
Message-ID: <3540b132-bc8e-0431-a955-17407028efa6@kernel.org> (raw)
In-Reply-To: <50ca78a649faf53f8941bc94c9cf8268b3644d38.1781666867.git.namcao@linutronix.de>
On Wed, 17 Jun 2026, Nam Cao wrote:
> This reverts commit 5d15d2ad36b0 ("riscv: hwprobe: Fix stale vDSO data for
> late-initialized keys at boot"). The commit ensures synchronization between
> the unaligned vector access speed probe kthread and vDSO data read. But now
> that the kthread has been removed, this commit can be reverted.
>
> Signed-off-by: Nam Cao <namcao@linutronix.de>
Thanks, will queue for v7.3.
- Paul
next prev parent reply other threads:[~2026-07-29 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 3:38 [PATCH 0/2] riscv: unaligned: stop using kthread for vector speed probe Nam Cao
2026-06-17 3:38 ` [PATCH 1/2] riscv: unaligned: stop using kthread for check_vector_unaligned_access() Nam Cao
2026-06-17 8:49 ` Nam Cao
2026-06-29 20:52 ` Jesse Taube
2026-07-29 19:31 ` Paul Walmsley
2026-06-17 3:38 ` [PATCH 2/2] Revert "riscv: hwprobe: Fix stale vDSO data for late-initialized keys at boot" Nam Cao
2026-07-29 19:32 ` Paul Walmsley [this message]
2026-06-17 14:21 ` [PATCH 0/2] riscv: unaligned: stop using kthread for vector speed probe Anirudh Srinivasan
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=3540b132-bc8e-0431-a955-17407028efa6@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=wangjingwei@iscas.ac.cn \
/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®