From: Yao Zi <me@ziyao.cc>
To: Paul Walmsley <pjw@kernel.org>, Han Gao <rabenda.cn@gmail.com>,
guoren@kernel.org
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
Alexandre Ghiti <alex@ghiti.fr>,
palmer@dabbelt.com, conor@kernel.org, paul.walmsley@sifive.com,
bjorn@rivosinc.com, eobras@redhat.com, corbet@lwn.net,
peterlin@andestech.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Leonardo Bras <leobras@redhat.com>
Subject: Re: [PATCH V2 2/2] riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup
Date: Thu, 15 Jan 2026 11:10:41 +0000 [thread overview]
Message-ID: <aWjLMYZ10iNxs1i6@pie> (raw)
In-Reply-To: <6c45ed33-d6f8-d385-8b89-9caf2ec18c77@kernel.org>
On Tue, Oct 14, 2025 at 09:37:47PM -0600, Paul Walmsley wrote:
> Hello Han Gao, Guo Ren,
>
> Sorry for the delay in responding -
>
> On Tue, Oct 7, 2025 at 11:36 PM Han Gao <rabenda.cn@gmail.com> wrote:
>
> > This patch is included in the 6.17 merge window but not in the
> > 6.18 merge window.
> > Is it possible that the patch was missed?
>
> This was almost sent upstream as part of the v6.18 merge window, but given
> that it adds the ability for architectures to override WRITE_ONCE, I think
> it needs one more attempt at gathering feedback before we do. I'll send
> that out this week.
>
> thanks for your patience,
Hi Paul,
Could this series be queued for 6.20? It has been more than two months,
and seems no more feedback has come up. Thanks for your work!
> - Paul
Best regards,
Yao Zi
next prev parent reply other threads:[~2026-01-15 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 15:53 [PATCH V2 0/2] riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup guoren
2025-07-13 15:53 ` [PATCH V2 1/2] riscv: Move vendor errata definitions to new header guoren
2025-07-15 13:13 ` Han Gao
2025-07-17 8:21 ` Alexandre Ghiti
2025-07-13 15:53 ` [PATCH V2 2/2] riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup guoren
2025-07-15 3:02 ` Drew Fustini
2025-07-15 6:14 ` Guo Ren
2025-07-15 13:14 ` Han Gao
2025-07-17 8:22 ` Alexandre Ghiti
2025-10-07 21:36 ` Han Gao
2025-10-09 7:29 ` Alexandre Ghiti
2025-10-15 3:37 ` Paul Walmsley
2025-10-15 7:53 ` Guo Ren
2025-12-12 16:37 ` Han Gao
2026-01-15 11:10 ` Yao Zi [this message]
2025-08-06 17:15 ` [PATCH V2 0/2] " patchwork-bot+linux-riscv
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=aWjLMYZ10iNxs1i6@pie \
--to=me@ziyao.cc \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=eobras@redhat.com \
--cc=guoren@kernel.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.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