From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Dirk Behme <dirk.behme@gmail.com>
Cc: Atharv Dubey <atharvd440@gmail.com>,
arnd@arndb.de, gregkh@linuxfoundation.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: miscdevice: use `pin_init::zeroed()` for C type initialization
Date: Sat, 29 Nov 2025 17:33:28 +0100 [thread overview]
Message-ID: <CANiq72mh=7nf7P67GFKpeO5temn+QCStPbwjGG2OUxDLPL970A@mail.gmail.com> (raw)
In-Reply-To: <071c5fcf-bd7d-40da-ad7c-c0edbe780671@gmail.com>
On Sat, Nov 29, 2025 at 7:46 AM Dirk Behme <dirk.behme@gmail.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
next prev parent reply other threads:[~2025-11-29 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 16:23 [PATCH] rust: miscdevice: use `pin_init::zeroed()` for C type initialization Atharv Dubey
2025-11-28 19:08 ` Miguel Ojeda
2025-11-29 6:46 ` Dirk Behme
2025-11-29 16:33 ` Miguel Ojeda [this message]
2025-12-01 14:24 ` Atharv Dubey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANiq72mh=7nf7P67GFKpeO5temn+QCStPbwjGG2OUxDLPL970A@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=atharvd440@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dirk.behme@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).