[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72mh=7nf7P67GFKpeO5temn+QCStPbwjGG2OUxDLPL970A@mail.gmail.com>
Date: Sat, 29 Nov 2025 17:33:28 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Dirk Behme <dirk.behme@...il.com>
Cc: Atharv Dubey <atharvd440@...il.com>, arnd@...db.de, gregkh@...uxfoundation.org,
ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, lossin@...nel.org,
a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu,
dakr@...nel.org, rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: miscdevice: use `pin_init::zeroed()` for C type initialization
On Sat, Nov 29, 2025 at 7:46 AM Dirk Behme <dirk.behme@...il.com> wrote:
>
> While getting rid of the `unsafe`what's about dropping the `SAFETY`
> comment as well? As done by Benno in [1]?
Yeah -- Atharv: please make sure to check your patches with `CLIPPY=1`
(which should detect that), `rustdoc`, `rusttest`... Some notes at:
https://rust-for-linux.com/contributing#submit-checklist-addendum
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists