From: FUJITA Tomonori <tomo@flapping.org>
To: ojeda@kernel.org
Cc: a.hindborg@kernel.org, acourbot@nvidia.com, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, gary@garyguo.net,
lossin@kernel.org, tamird@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: [PATCH v1 0/2] rust: bug: add warn_once macro
Date: Sat, 3 Oct 2026 21:39:01 +0900 [thread overview]
Message-ID: <20261003123903.113572-1-tomo@flapping.org> (raw)
From: FUJITA Tomonori <fujita.tomonori@gmail.com>
This series adds `warn_once!`, the Rust version of C `WARN_ONCE()`.
Patch 1 documents when to use the WARN macros, based on the comment in
include/asm-generic/bug.h. Patch 2 adds `warn_once!`.
Miguel, patch 2 moves the UML `warn_slowpath_fmt()` call into
`warn_slowpath()` and updates its SAFETY comment, so [1] can be dropped
if this series is applied.
[1] https://lore.kernel.org/rust-for-linux/20261002104550.2877930-1-tomo@flapping.org/
FUJITA Tomonori (2):
rust: bug: document when to use the WARN macros
rust: bug: add warn_once macro
rust/helpers/bug.c | 11 ++++
rust/kernel/bug.rs | 134 +++++++++++++++++++++++++++++++++++++++++----
2 files changed, 135 insertions(+), 10 deletions(-)
base-commit: d52549881e6777fdcc79a349028413b182a641d2
--
2.43.0
next reply other threads:[~2026-10-03 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 12:39 FUJITA Tomonori [this message]
2026-10-03 12:39 ` [PATCH v1 1/2] rust: bug: document when to use the WARN macros FUJITA Tomonori
2026-10-04 8:08 ` Andreas Hindborg
2026-10-03 12:39 ` [PATCH v1 2/2] rust: bug: add warn_once macro 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=20261003123903.113572-1-tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--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=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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