linux-kernel - Re: [PATCH v6 0/4] RISC-V: re-enable gcc + rust builds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47d1dab9-a379-7b3a-d06c-03d674cfbb76@kernel.org>
Date: Sat, 24 Jan 2026 00:47:26 -0700 (MST)
From: Paul Walmsley <pjw@...nel.org>
To: Asuna Yang <xinrui.riscv@...c.iscas.ac.cn>
cc: Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>, 
    Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>, 
    Gary Guo <gary@...yguo.net>, 
    Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
    Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
    Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
    Danilo Krummrich <dakr@...nel.org>, 
    Nick Desaulniers <nick.desaulniers+lkml@...il.com>, 
    Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>, 
    Paul Walmsley <pjw@...nel.org>, Palmer Dabbelt <palmer@...belt.com>, 
    Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>, 
    Jonathan Corbet <corbet@....net>, Conor Dooley <conor@...nel.org>, 
    Mingcong Bai <jeffbai@...c.io>, Han Gao <rabenda.cn@...il.com>, 
    Vivian Wang <wangruikang@...as.ac.cn>, 
    Jason Montleon <jmontleo@...hat.com>, linux-kbuild@...r.kernel.org, 
    linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org, 
    llvm@...ts.linux.dev, linux-riscv@...ts.infradead.org, 
    linux-doc@...r.kernel.org
Subject: Re: [PATCH v6 0/4] RISC-V: re-enable gcc + rust builds

Hi Asuna,

On Thu, 22 Jan 2026, Asuna Yang wrote:

> Gently ping. I think this patch is ready for review. Is there anything else I
> need to do before merging?

I guess this should probably go in via the arch/riscv tree?  If you agree, 
then from a maintenance point of view, it would be good to get some acks 
for the first and third patches from the relevant maintainers.


thanks,

- Paul