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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260129-removed-audacity-398bc9363728@spud>
Date: Thu, 29 Jan 2026 09:30:04 +0000
From: Conor Dooley <conor@...nel.org>
To: Paul Walmsley <pjw@...nel.org>
Cc: Asuna Yang <xinrui.riscv@...c.iscas.ac.cn>,
	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>,
	Palmer Dabbelt <palmer@...belt.com>,
	Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>,
	Jonathan Corbet <corbet@....net>, 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

On Sat, Jan 24, 2026 at 12:47:26AM -0700, Paul Walmsley wrote:
> 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.

Not a rust maintainer of course, but from a "I was involved in this and
haven't replied in a while to the versions" point of view:
Acked-by: Conor Dooley <conor.dooley@...rochip.com>

I've just not had the time to test this and so I've been putting off
replying, but the idea is what I wanted to have done and I appreciate
the work done on it by Asuna, so I'm acking it now rather than stalling
until I can test and give an r-b. It's the right thing to do for a !gcc
point of view too in my opinion, even if the possible issues are
unlikely to manifest.

Cheers,
Conor.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)