All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, ojeda@kernel.org,
	 alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
	 bjorn3_gh@protonmail.com, benno.lossin@proton.me,
	a.hindborg@kernel.org,  tmgross@umich.edu, airlied@gmail.com,
	acourbot@nvidia.com,  jhubbard@nvidia.com,
	linux-kernel@vger.kernel.org,  rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v3 1/5] rust: types: add `Opaque::zeroed`
Date: Thu, 20 Mar 2025 08:37:35 +0000	[thread overview]
Message-ID: <Z9vTzya716bkk4bt@google.com> (raw)
In-Reply-To: <20250319203455.132539-2-dakr@kernel.org>

On Wed, Mar 19, 2025 at 09:33:53PM +0100, Danilo Krummrich wrote:
> Analogous to `Opaque::uninit` add `Opaque::zeroed`, which sets the
> corresponding memory to zero. In contrast to `Opaque::uninit`, the
> corresponding value, depending on its type, may be initialized.
> 
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>

Reviewed-by: Alice Ryhl <aliceryhl@google.com>

  reply	other threads:[~2025-03-20  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 20:33 [PATCH v3 0/5] Auxiliary bus Rust abstractions Danilo Krummrich
2025-03-19 20:33 ` [PATCH v3 1/5] rust: types: add `Opaque::zeroed` Danilo Krummrich
2025-03-20  8:37   ` Alice Ryhl [this message]
2025-03-19 20:33 ` [PATCH v3 2/5] driver: core: auxiliary: export auxiliary_bus_type Danilo Krummrich
2025-03-19 20:33 ` [PATCH v3 3/5] rust: auxiliary: add auxiliary device / driver abstractions Danilo Krummrich
2025-03-19 20:33 ` [PATCH v3 4/5] rust: auxiliary: add auxiliary registration Danilo Krummrich
2025-03-19 20:33 ` [PATCH v3 5/5] samples: rust: add Rust auxiliary driver sample Danilo Krummrich

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=Z9vTzya716bkk4bt@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.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=gregkh@linuxfoundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rafael@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 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.