From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Yury Norov" <yury.norov@gmail.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>, "Edwin Peer" <epeer@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Steven Price" <steven.price@arm.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/7] rust: num: add `as_bool` method to `Bounded<_, 1>`
Date: Thu, 12 Feb 2026 21:55:09 +0900 [thread overview]
Message-ID: <DGCZZASC04RD.1CF5NXQ95XJ8B@nvidia.com> (raw)
In-Reply-To: <879031CB-A9A6-486A-8E01-E557ABB01F41@collabora.com>
On Sat Feb 7, 2026 at 3:28 AM JST, Daniel Almeida wrote:
>
>
>> On 29 Jan 2026, at 10:32, Alexandre Courbot <acourbot@nvidia.com> wrote:
>>
>> Single-bit numbers are typically treated as booleans. There is an
>> `Into<bool>` implementation for those, but invoking it from contexts
>> that lack type expectations is not always convenient.
>>
>> Add an `as_bool` method as a simpler shortcut.
>>
>> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
>> Reviewed-by: Gary Guo <gary@garyguo.net>
>> Tested-by: Dirk Behme <dirk.behme@de.bosch.com>
>> Acked-by: Miguel Ojeda <ojeda@kernel.org>
>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>> ---
>> rust/kernel/num/bounded.rs | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>>
>> diff --git a/rust/kernel/num/bounded.rs b/rust/kernel/num/bounded.rs
>> index 4b929762d5c2..b41ca6df1525 100644
>> --- a/rust/kernel/num/bounded.rs
>> +++ b/rust/kernel/num/bounded.rs
>> @@ -1098,3 +1098,24 @@ fn from(value: bool) -> Self {
>> Self::__new(T::from(value))
>> }
>> }
>> +
>> +impl<T> Bounded<T, 1>
>> +where
>> + T: Integer + Zeroable,
>> +{
>> + /// Returns the value of this [`Bounded`] as a [`bool`].
>> + ///
>> + /// This is a shorter way of writing `bool::from(self)`.
>> + ///
>> + /// # Examples
>> + ///
>> + /// ```
>> + /// use kernel::num::Bounded;
>> + ///
>> + /// assert_eq!(Bounded::<u8, 1>::new::<0>().as_bool(), false);
>> + /// assert_eq!(Bounded::<u8, 1>::new::<1>().as_bool(), true);
>> + /// ```
>> + pub fn as_bool(self) -> bool {
>> + self.into()
>> + }
>> +}
>>
>> --
>> 2.52.0
>>
>
> I wonder whether this should be into_bool() instead? as_foo() usually goes from &self to &Foo.
Yup, that's definitely what this method should be called. Thanks for
pointing it out.
next prev parent reply other threads:[~2026-02-12 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 13:32 [PATCH v5 0/7] rust: add `register!` macro Alexandre Courbot
2026-01-29 13:32 ` [PATCH v5 1/7] rust: enable the `generic_arg_infer` feature Alexandre Courbot
2026-01-29 13:32 ` [PATCH v5 2/7] rust: num: add `shr` and `shl` methods to `Bounded` Alexandre Courbot
2026-02-06 18:23 ` Daniel Almeida
2026-01-29 13:32 ` [PATCH v5 3/7] rust: num: add `as_bool` method to `Bounded<_, 1>` Alexandre Courbot
2026-02-06 18:28 ` Daniel Almeida
2026-02-12 12:55 ` Alexandre Courbot [this message]
2026-01-29 13:32 ` [PATCH v5 4/7] rust: num: add `into_inner` method to `Bounded` Alexandre Courbot
2026-02-06 18:29 ` Daniel Almeida
2026-01-29 13:32 ` [PATCH v5 5/7] rust: io: add `register!` macro Alexandre Courbot
2026-02-06 19:02 ` Danilo Krummrich
2026-02-06 21:11 ` Daniel Almeida
2026-01-29 13:32 ` [PATCH v5 6/7] sample: rust: pci: use " Alexandre Courbot
2026-02-06 18:57 ` Danilo Krummrich
2026-01-29 13:32 ` [PATCH FOR REFERENCE v5 7/7] gpu: nova-core: use the kernel " Alexandre Courbot
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=DGCZZASC04RD.1CF5NXQ95XJ8B@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dirk.behme@de.bosch.com \
--cc=ecourtney@nvidia.com \
--cc=epeer@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=yury.norov@gmail.com \
/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