From: "Danilo Krummrich" <dakr@kernel.org>
To: "Ke Sun" <sunke@kylinos.cn>
Cc: rust-for-linux@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Subject: Re: [PATCH v2 4/7] rust: debugfs: use pin_init::zeroed() for file_operations
Date: Sun, 25 Jan 2026 23:45:32 +0100 [thread overview]
Message-ID: <DFY19ISM6K8S.RC3Q66OPMKUA@kernel.org> (raw)
In-Reply-To: <20260120083824.477339-5-sunke@kylinos.cn>
On Tue Jan 20, 2026 at 9:38 AM CET, Ke Sun wrote:
> Replace unsafe core::mem::zeroed() with pin_init::zeroed() for
> file_operations initialization in all debugfs file operation
> implementations.
>
> Signed-off-by: Ke Sun <sunke@kylinos.cn>
Applied to driver-core-testing, thanks!
next prev parent reply other threads:[~2026-01-25 22:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 8:38 [PATCH v2 0/7] rust: Replace unsafe core::mem::zeroed() with pin_init::zeroed() Ke Sun
2026-01-20 8:38 ` [PATCH v2 1/7] rust: auxiliary: use pin_init::zeroed() instead of unsafe zeroed Ke Sun
2026-01-20 8:38 ` [PATCH v2 2/7] rust: block: mq: use pin_init::zeroed() for queue_limits Ke Sun
2026-01-21 9:51 ` Andreas Hindborg
2026-01-20 8:38 ` [PATCH v2 3/7] rust: block: mq: use pin_init::zeroed() for tag_set Ke Sun
2026-01-21 9:52 ` Andreas Hindborg
2026-01-20 8:38 ` [PATCH v2 4/7] rust: debugfs: use pin_init::zeroed() for file_operations Ke Sun
2026-01-25 22:45 ` Danilo Krummrich [this message]
2026-01-20 8:38 ` [PATCH v2 5/7] rust: of: use pin_init::zeroed() instead of unsafe zeroed Ke Sun
2026-01-20 8:38 ` [PATCH v2 6/7] rust: pwm: use pin_init::zeroed() for pwm_ops Ke Sun
2026-01-20 8:38 ` [PATCH v2 7/7] rust: security: use pin_init::zeroed() for lsm_context Ke Sun
2026-01-20 16:04 ` [PATCH v2 0/7] rust: Replace unsafe core::mem::zeroed() with pin_init::zeroed() Gary Guo
2026-01-21 14:47 ` (subset) " Jens Axboe
2026-01-25 19:24 ` Miguel Ojeda
2026-01-27 5:56 ` Ke Sun
2026-01-27 10:05 ` Miguel Ojeda
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=DFY19ISM6K8S.RC3Q66OPMKUA@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sunke@kylinos.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.