[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aS2lJXfXy0fhc_F-@atharv-HP-Pavilion-x360-2-in-1-Laptop-14-ek1xxx>
Date: Mon, 1 Dec 2025 19:54:37 +0530
From: Atharv Dubey <atharvd440@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Dirk Behme <dirk.behme@...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 05:33:28PM +0100, Miguel Ojeda wrote:
> 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
>Sure,will keep this in mind while sending out patches.
-Atharv
Powered by blists - more mailing lists