rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Burak Emir <bqe@google.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Yury Norov" <yury.norov@gmail.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Todd Kjos" <tkjos@android.com>,
	"Martijn Coenen" <maco@android.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Carlos Llamas" <cmllamas@google.com>,
	"Suren Baghdasaryan" <surenb@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>,
	"Danilo Krummrich" <dakr@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/6] rust: bitmap: add MAX_LEN and MAX_INLINE_LEN constants
Date: Tue, 25 Nov 2025 15:32:31 +0100	[thread overview]
Message-ID: <CACQBu=VBf0KzP9mjYVFFbzGcwfPCciUtY93tajzsNa19Trn3Rg@mail.gmail.com> (raw)
In-Reply-To: <20251125-binder-bitmap-v6-1-dedaf1d05a98@google.com>

On Tue, Nov 25, 2025 at 2:59 PM Alice Ryhl <aliceryhl@google.com> wrote:
>
> To avoid hard-coding these values in drivers, define constants for them
> that drivers can reference. Also, update all instances in bitmap.rs and
> id_pool.rs that use these values to use the new constants.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>

Reviewed-by: Burak Emir <bqe@google.com>

  reply	other threads:[~2025-11-25 14:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 13:59 [PATCH v6 0/6] Use Rust Bitmap from Rust Binder driver Alice Ryhl
2025-11-25 13:59 ` [PATCH v6 1/6] rust: bitmap: add MAX_LEN and MAX_INLINE_LEN constants Alice Ryhl
2025-11-25 14:32   ` Burak Emir [this message]
2025-11-25 13:59 ` [PATCH v6 2/6] rust: bitmap: add BitmapVec::new_inline() Alice Ryhl
2025-11-25 13:59 ` [PATCH v6 3/6] rust: id_pool: rename IdPool::new() to with_capacity() Alice Ryhl
2025-11-25 13:59 ` [PATCH v6 4/6] rust: id_pool: do not supply starting capacity Alice Ryhl
2025-11-25 13:59 ` [PATCH v6 5/6] rust: id_pool: do not immediately acquire new ids Alice Ryhl
2025-11-25 13:59 ` [PATCH v6 6/6] rust_binder: use bitmap for allocation of handles Alice Ryhl
2025-11-26  2:26   ` Yury Norov
2025-11-26  8:17     ` Burak Emir
2025-11-26  8:35     ` Alice Ryhl
2025-11-26 15:31       ` Yury Norov
2025-11-26 15:56         ` Alice Ryhl
2025-11-26 16:13           ` Yury Norov
2025-11-26 16:22             ` Alice Ryhl

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='CACQBu=VBf0KzP9mjYVFFbzGcwfPCciUtY93tajzsNa19Trn3Rg@mail.gmail.com' \
    --to=bqe@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=maco@android.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=tkjos@android.com \
    --cc=tmgross@umich.edu \
    --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;
as well as URLs for NNTP newsgroup(s).