linux-kernel - Re: [PATCH v2 15/22] rust: make pin-init its own crate

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: <871puulg7k.fsf@kernel.org>
Date: Tue, 18 Mar 2025 12:40:31 +0100
From: Andreas Hindborg <a.hindborg@...nel.org>
To: "Benno Lossin" <benno.lossin@...ton.me>
Cc: "Miguel Ojeda" <ojeda@...nel.org>,  "Alex Gaynor"
 <alex.gaynor@...il.com>,  "Boqun Feng" <boqun.feng@...il.com>,  "Gary Guo"
 <gary@...yguo.net>,  Björn Roy Baron
 <bjorn3_gh@...tonmail.com>,  "Alice
 Ryhl" <aliceryhl@...gle.com>,  "Trevor Gross" <tmgross@...ch.edu>,
  "Danilo Krummrich" <dakr@...nel.org>,  "Greg Kroah-Hartman"
 <gregkh@...uxfoundation.org>,  "Rafael J. Wysocki" <rafael@...nel.org>,
  "Peter Zijlstra" <peterz@...radead.org>,  "Ingo Molnar"
 <mingo@...hat.com>,  "Will Deacon" <will@...nel.org>,  "Waiman Long"
 <longman@...hat.com>,  "Fiona Behrens" <me@...enk.dev>,
  <linux-kernel@...r.kernel.org>,  <rust-for-linux@...r.kernel.org>,
  <linux-block@...r.kernel.org>
Subject: Re: [PATCH v2 15/22] rust: make pin-init its own crate

"Benno Lossin" <benno.lossin@...ton.me> writes:

> Rename relative paths inside of the crate to still refer to the same
> items, also rename paths inside of the kernel crate and adjust the build
> system to build the crate.
>
> Enable the `lint_reasons` feature for the `macros` crate in order to be
> able to use `expect`. The feature is stable since Rust 1.81.0, so we
> only need to enable the feature for older compiler versions.
>
> Signed-off-by: Benno Lossin <benno.lossin@...ton.me>
> Reviewed-by: Fiona Behrens <me@...enk.dev>
> Tested-by: Andreas Hindborg <a.hindborg@...nel.org>

Reviewed-by: Andreas Hindborg <a.hindborg@...nel.org>

Best regards,
Andreas Hindborg