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
| ||
|
Message-ID: <CANiq72=Ugc4bqJCQxnAOw1f3gtD-a_aYdrjbCp4A0aX2hqDaVA@mail.gmail.com> Date: Sat, 28 Oct 2023 17:11:49 +0200 From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> To: Benno Lossin <benno.lossin@...ton.me> Cc: Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>, FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, tmgross@...ch.edu, wedsonaf@...il.com Subject: Re: [PATCH net-next v7 0/5] Rust abstractions for network PHY drivers On Sat, Oct 28, 2023 at 1:41 PM Benno Lossin <benno.lossin@...ton.me> wrote: > > We have it disabled on the `pub mod code` in error.rs line 20: > https://elixir.bootlin.com/linux/latest/source/rust/kernel/error.rs#L20 Thanks Benno -- I checked the `rust` branch, and forgot about that one. It is an interesting example though, because it could have gone either way: we were not using it for the same code in the `rust` branch -- it was an aesthetic improvement for consistency. In fact, if we do the macro differently, it would not be needed. Cheers, Miguel
Powered by blists - more mailing lists