linux-kernel - Re: [PATCH] rust: kconfig: Don't require RUST_IS

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 for Android: free password hash cracker in your pocket

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

Message-Id: <177016418652.1146354.981060291224113155.b4-ty@kernel.org>
Date: Tue, 03 Feb 2026 17:16:26 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Miguel Ojeda <ojeda@...nel.org>, Matthew Maurer <mmaurer@...gle.com>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, 
 rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] rust: kconfig: Don't require RUST_IS_AVAILABLE for
 rustc-option

On Tue, 09 Sep 2025 18:14:20 +0000, Matthew Maurer wrote:
> The final version of this macro does not fail in the absence of an
> invokable `$(RUSTC)`, so we don't need to be careful not to invoke it.
> 
> 

Applied to

  https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next

Thanks!

[1/1] rust: kconfig: Don't require RUST_IS_AVAILABLE for rustc-option
      https://git.kernel.org/kbuild/c/f2445d6f264c6

Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.

Best regards,
-- 
Nathan Chancellor <nathan@...nel.org>