From: Sami Tolvanen <samitolvanen@google.com>
To: "Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Daniel Gomez" <da.gomez@kernel.org>,
"Aaron Tomlin" <atomlin@atomlin.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: module_param: use `pr_warn_once!` for null pointer warning
Date: Tue, 26 May 2026 23:40:39 +0000 [thread overview]
Message-ID: <177983883957.35274.15506019019254966722.b4-ty@google.com> (raw)
In-Reply-To: <20260427-params-pr-once-v1-1-3a8c64704cc4@kernel.org>
On Mon, 27 Apr 2026 10:11:35 +0200, Andreas Hindborg wrote:
> Replace `pr_warn!` and the accompanying TODO with `pr_warn_once!`, now that
> the macro is available.
>
>
Applied to modules-next, thanks!
[1/1] rust: module_param: use `pr_warn_once!` for null pointer warning
commit: 8d2a562b7efe98fdea57d10caaced911fca46a3f
Best regards,
Sami
next prev parent reply other threads:[~2026-05-26 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 8:11 [PATCH] rust: module_param: use `pr_warn_once!` for null pointer warning Andreas Hindborg
2026-04-27 11:28 ` Daniel Gomez
2026-04-27 13:36 ` Gary Guo
2026-04-29 23:21 ` Aaron Tomlin
2026-05-18 17:43 ` Miguel Ojeda
2026-05-18 21:47 ` Sami Tolvanen
2026-05-26 23:40 ` Sami Tolvanen [this message]
2026-05-26 23:46 ` Miguel Ojeda
2026-05-26 23:59 ` Sami Tolvanen
-- strict thread matches above, loose matches on Subject: below --
2026-06-06 18:24 [PATCH] rust: module_param: use pr_warn_once! " Maurice Hieronymus
2026-06-06 20:15 ` 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=177983883957.35274.15506019019254966722.b4-ty@google.com \
--to=samitolvanen@google.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=atomlin@atomlin.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=da.gomez@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--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