From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: "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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: num: bounded: rename `try_into_bitint` to `try_into_bounded`
Date: Mon, 24 Nov 2025 17:14:24 +0100 [thread overview]
Message-ID: <CANiq72kdrPx5uUVqnHpF88b8y0-gOTKVSfTDq2ZZVJ6B6WxzSg@mail.gmail.com> (raw)
In-Reply-To: <20251124-bounded_fix-v1-1-d8e34e1c727f@nvidia.com>
On Mon, Nov 24, 2025 at 2:50 PM Alexandre Courbot <acourbot@nvidia.com> wrote:
>
> This is a remnant from when `Bounded` was called `BitInt` which I didn't
> rename. Fix this.
>
> Fixes: 01e345e82ec3 ("rust: num: add Bounded integer wrapping type")
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Applied to `rust-next` -- thanks!
Hmm... This is the sort of thing where I am not sure if it should
count as a fix, since while it is unexpected, there is nothing
actually broken. I kept the tag since you provided it anyway.
Cheers,
Miguel
prev parent reply other threads:[~2025-11-24 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 13:50 [PATCH] rust: num: bounded: rename `try_into_bitint` to `try_into_bounded` Alexandre Courbot
2025-11-24 16:14 ` Miguel Ojeda [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=CANiq72kdrPx5uUVqnHpF88b8y0-gOTKVSfTDq2ZZVJ6B6WxzSg@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).