From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: "Benno Lossin" <benno.lossin@proton.me>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rust: pin-init: improve documentation for `Zeroable` derive macros
Date: Sat, 26 Apr 2025 13:36:18 +0200 [thread overview]
Message-ID: <3d214f39-e529-45ce-b6f7-9dd50d0e119c@gmail.com> (raw)
In-Reply-To: <20250426083901.13289-2-benno.lossin@proton.me>
On 26.04.25 10:39 AM, Benno Lossin wrote:
> Specify that both `MaybeZeroable` and `Zeroable` work on `union`s. Add a
> doc example for a union. Also include an example with visibility on the
> field.
>
> Link: https://github.com/Rust-for-Linux/pin-init/pull/48/commits/ab0985a0e08df06c60a32ca5888f74adcc2c1cf3
> Signed-off-by: Benno Lossin <benno.lossin@proton.me>
> ---
> Also see the compile-fail & macro expansion tests added by this commit
> (not included in the kernel, since the test files are only upstream):
>
> https://github.com/Rust-for-Linux/pin-init/pull/48/commits/278070d12b41f0fca1b0d6dff6c5f38f3cf46044
> ---
Reviewed-by: Christian Schrefl <chrisi.schrefl@gmail.com>
next prev parent reply other threads:[~2025-04-26 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 8:39 [PATCH 1/2] rust: pin-init: fix typos Benno Lossin
2025-04-26 8:39 ` [PATCH 2/2] rust: pin-init: improve documentation for `Zeroable` derive macros Benno Lossin
2025-04-26 11:36 ` Christian Schrefl [this message]
2025-04-26 10:48 ` [PATCH 1/2] rust: pin-init: fix typos Christian Schrefl
2025-05-01 16:38 ` Benno Lossin
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=3d214f39-e529-45ce-b6f7-9dd50d0e119c@gmail.com \
--to=chrisi.schrefl@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--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