[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87o6z8h4im.fsf@kernel.org>
Date: Tue, 11 Feb 2025 16:42:25 +0100
From: Andreas Hindborg <a.hindborg@...nel.org>
To: <jens.korinth@...a.io>
Cc: "Jens Korinth via B4 Relay" <devnull+jens.korinth.tuta.io@...nel.org>,
"Miguel Ojeda" <ojeda@...nel.org>, "Alex Gaynor"
<alex.gaynor@...il.com>, "Boqun Feng" <boqun.feng@...il.com>, "Gary Guo"
<gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, "Benno
Lossin" <benno.lossin@...ton.me>, "Alice Ryhl" <aliceryhl@...gle.com>,
"Trevor Gross" <tmgross@...ch.edu>, "Rust For Linux"
<rust-for-linux@...r.kernel.org>, "FUJITA Tomonori"
<fujita.tomonori@...il.com>, "Dirk Behme" <dirk.behme@...il.com>, "Linux
Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/3] rust: Add pr_*_once macros
<jens.korinth@...a.io> writes:
> Hi!
>
>> Thanks for the patch! Do you plan on sending a new version? If not, do you mind if I send v5?
>
> I think there is currently no consensus on how exactly it should be done (or at least I was confused about that). If you’re actively using the patch please go ahead! Active usage is always the best argument in such cases.
I was informed this patch set is the correct way to emit a warning in
the module_params patch set [1].
I did not follow all the discussion so I am not sure either. But I'll
look into the discussion then.
Best regards,
Andreas Hindborg
[1] https://lore.kernel.org/rust-for-linux/20250204-module-params-v3-v5-0-bf5ec2041625@kernel.org/
Powered by blists - more mailing lists