Linux Modules
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Wenzhao Liao <wenzhaoliao@ruc.edu.cn>,
	mcgrof@kernel.org, petr.pavlu@suse.com, da.gomez@kernel.org,
	samitolvanen@google.com, ojeda@kernel.org,
	linux-modules@vger.kernel.org, rust-for-linux@vger.kernel.org,
	atomlin@atomlin.com, boqun@kernel.org, gary@garyguo.net,
	bjorn3_gh@protonmail.com, lossin@kernel.org,
	aliceryhl@google.com, tmgross@umich.edu, dakr@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] rust: module_param: support bool parameters
Date: Thu, 28 May 2026 15:15:28 +0200	[thread overview]
Message-ID: <87fr3b7k0f.fsf@t14s.mail-host-address-is-not-set> (raw)
In-Reply-To: <2026041323-fled-sharply-77c0@gregkh>

Greg KH <greg@kroah.com> writes:

> On Mon, Apr 13, 2026 at 02:00:17PM +0200, Andreas Hindborg wrote:
>> "Greg KH" <greg@kroah.com> writes:
>> 
>> > On Sat, Apr 11, 2026 at 09:02:53AM -0400, Wenzhao Liao wrote:
>> >> Sorry for the earlier noise and for our unfamiliarity with parts of the
>> >> kernel submission process, which created extra burden for maintainers.
>> >>
>> >> This patch adds boolean module parameter support to the Rust `module!`
>> >> parameter path.
>> >>
>> >> It implements `ModuleParam` for `bool` and wires `PARAM_OPS_BOOL` into
>> >> the Rust module parameter machinery, so Rust-side parsing reuses the
>> >> existing kernel `kstrtobool()` semantics through `kstrtobool_bytes()`
>> >> instead of introducing a separate parser. A boolean parameter is also
>> >> added to `samples/rust/rust_minimal.rs` as a small reference user and
>> >> build-time validation point.
>> >
>> > What driver needs this feature?  Module options should be very rare
>> > going forward as they are 1990's technology and do not fit the "modern"
>> > kernel model at all.
>> 
>> Rust null block uses module parameters, and was requested to use proper
>> boolean parsing rather than overloading u8 parsing for boolean
>> parameters [1].
>> 
>> Best regards,
>> Andreas Hindborg
>> 
>> 
>> [1] https://lore.kernel.org/rust-for-linux/abfK4eji5jKSeO_W@google.com/
>> 
>
> Ok, then that needs to be said somewhere, and ideally, have the code
> that uses that as part of the patch series.

It should be mentioned for sure, with a link to the code. I'm not sure
including this patch in the rnull driver series is the right approach.
That series is a really long already. I think using the b4 dependency
feature for dependencies is a better approach for marking dependencies.

I understand that you want to see APIs in context of use, that makes
sense.


Best regards,
Andreas Hindborg





      reply	other threads:[~2026-05-28 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 13:02 [PATCH 0/1] rust: module_param: support bool parameters Wenzhao Liao
2026-04-11 13:02 ` [PATCH 1/1] " Wenzhao Liao
2026-04-27  8:04   ` Andreas Hindborg
2026-04-11 13:20 ` [PATCH 0/1] " Greg KH
2026-04-13 12:00   ` Andreas Hindborg
2026-04-13 12:25     ` Greg KH
2026-05-28 13:15       ` Andreas Hindborg [this message]

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=87fr3b7k0f.fsf@t14s.mail-host-address-is-not-set \
    --to=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=greg@kroah.com \
    --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=samitolvanen@google.com \
    --cc=tmgross@umich.edu \
    --cc=wenzhaoliao@ruc.edu.cn \
    /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