linux-kernel - Re: [PATCH] loongarch: rust: Switch to use built-in rustc target

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: <CANiq72mHCNU2wGpELBbgOA8LKQhm_-RyG8+9bP9miYJOkUw2Uw@mail.gmail.com>
Date: Tue, 5 Mar 2024 11:10:12 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Huacai Chen <chenhuacai@...nel.org>
Cc: WANG Rui <wangrui@...ngson.cn>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>, 
	Alice Ryhl <aliceryhl@...gle.com>, Jamie Cunliffe <Jamie.Cunliffe@....com>, 
	Catalin Marinas <catalin.marinas@....com>, WANG Xuerui <kernel@...0n.name>, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	loongarch@...ts.linux.dev, loongson-kernel@...ts.loongnix.cn
Subject: Re: [PATCH] loongarch: rust: Switch to use built-in rustc target

On Tue, Mar 5, 2024 at 10:58 AM Huacai Chen <chenhuacai@...nel.org> wrote:
>
> The base of the loongarch tree doesn't contain the arm64 modifications
> now, so this patch is better to be applied on the rust tree with my
> Acked-by. But if you have some trouble doing that, I can also manually
> merge the arm64 parts to the loongarch tree, and then apply this
> patch. Thanks.

The rust tree doesn't have the arm64 changes either (i.e. they are in
the arm64 tree), so we would have the same issue.

Since it is quite late and there is no rush for this, I would suggest
applying it after the merge window in loongarch64 and thus avoiding a
merge. But, of course, up to you!

Thanks!

Cheers,
Miguel