All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: alex.gaynor@gmail.com, ojeda@kernel.org, a.hindborg@kernel.org,
	 boqun.feng@gmail.com, bjorn3_gh@protonmail.com, dakr@kernel.org,
	 gary@garyguo.net, lossin@kernel.org,
	rust-for-linux@vger.kernel.org,  tmgross@umich.edu
Subject: Re: [PATCH v3 1/2] rust: Add support for calling a function exactly once
Date: Thu, 18 Dec 2025 11:38:04 +0000	[thread overview]
Message-ID: <aUPnnL4kg9yiWtZn@google.com> (raw)
In-Reply-To: <20251117002452.4068692-2-fujita.tomonori@gmail.com>

On Mon, Nov 17, 2025 at 09:24:51AM +0900, FUJITA Tomonori wrote:
> Add the Rust equivalent of the kernel's `DO_ONCE_LITE` macro. While it
> would be possible to implement the feature entirely as a Rust macro,
> the functionality that can be implemented as regular functions has
> been extracted and implemented as the `OnceLite` struct for better
> code maintainability.
> 
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>

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

  reply	other threads:[~2025-12-18 11:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  0:24 [PATCH v3 0/2] Add support for print exactly once FUJITA Tomonori
2025-11-17  0:24 ` [PATCH v3 1/2] rust: Add support for calling a function " FUJITA Tomonori
2025-12-18 11:38   ` Alice Ryhl [this message]
2025-12-23  6:49     ` FUJITA Tomonori
2025-12-23 12:18   ` Gary Guo
2025-12-25  6:14     ` FUJITA Tomonori
2025-11-17  0:24 ` [PATCH v3 2/2] rust: Add pr_*_once macros FUJITA Tomonori
2025-12-23 12:06   ` Gary Guo
2025-12-25  6:29     ` FUJITA Tomonori
2026-01-13  6:52     ` FUJITA Tomonori
2025-12-18 11:18 ` [PATCH v3 0/2] Add support for print exactly once FUJITA Tomonori
2026-01-30  4:51 ` Miguel Ojeda
2026-01-30 12:34   ` FUJITA Tomonori

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=aUPnnL4kg9yiWtZn@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --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 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.