dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Eliot Courtney" <ecourtney@nvidia.com>,
	"Miguel Ojeda" <ojeda@kernel.org>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
	"Burak Emir" <burak.emir@gmail.com>,
	"Yury Norov" <yury.norov@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "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>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Onur Özkan" <work@onurozkan.dev>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Timur Tabi" <ttabi@nvidia.com>, "Zhi Wang" <zhiw@nvidia.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
	"Yury Norov" <ynorov@nvidia.com>
Subject: Re: [PATCH v9 0/9] rust: Add support for reserving of ranges of IDs
Date: Fri, 09 Oct 2026 00:04:57 +0900	[thread overview]
Message-ID: <DLZJSCA10YBI.2NIG6CA24G8L@nvidia.com> (raw)
In-Reply-To: <20260930-chid-v9-0-0d6cca376cff@nvidia.com>

On Wed Sep 30, 2026 at 11:42 AM JST, Eliot Courtney wrote:
<...>
> Eliot Courtney (9):
>       rust: bitmap: use function-level cfg on kunit test
>       rust: bitmap: restrict bitmap length to at most i32::MAX
>       rust: sizes: add sub-1K size constants
>       rust: sizes: implement SizeConstants for Alignment
>       rust: use Alignment size constants
>       rust: bitmap: add contiguous area operations
>       rust: id_pool: add contiguous ID reservation
>       rust: id_pool: do not round capacity up to BitmapVec::MAX_INLINE_LEN
>       gpu: nova-core: add ChannelIdPool

I am wondering about the merge path for this series (and the `cv` one).
We would like to use it for 7.4 in `drm-rust-next`, but given the
current timing we can either merge it there after `-rc1` is tagged, or
take the bits that apply on `nust-next` now.

The bits that apply being:

- Patch 1 of the `cv!` series [1],
- Patches 1-4 and 6-7 of this series.

(patch 5 touches mostly nova-core and doesn't apply on `rust-next`,
patch 8 lacks the required tags, and patch 9 is a nova-core patch)

Since that's quite a bit of code outside of nova-core, maybe it is
better to merge the non-nova bits mentioned above through the Rust tree
in time for the 7.4 merge window. All the patches I have listed should
have the required tags, but the `cv!` patch needs one last respin to
address the remaining comments and add a "Pitfalls" section at the very
least. Miguel, does that sound doable?

[1] https://lore.kernel.org/all/20260917-cv-v4-1-547ef5727451@nvidia.com/

      parent reply	other threads:[~2026-10-08 15:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  2:42 [PATCH v9 0/9] rust: Add support for reserving of ranges of IDs Eliot Courtney
2026-09-30  2:42 ` [PATCH v9 1/9] rust: bitmap: use function-level cfg on kunit test Eliot Courtney
2026-09-30  2:42 ` [PATCH v9 2/9] rust: bitmap: restrict bitmap length to at most i32::MAX Eliot Courtney
2026-09-30  2:42 ` [PATCH v9 3/9] rust: sizes: add sub-1K size constants Eliot Courtney
2026-09-30  9:12   ` Miguel Ojeda
2026-09-30 11:04     ` Alexandre Courbot
2026-09-30 11:22       ` Miguel Ojeda
2026-10-01  0:40         ` Gary Guo
2026-10-01  5:23           ` Eliot Courtney
2026-09-30  2:42 ` [PATCH v9 4/9] rust: sizes: implement SizeConstants for Alignment Eliot Courtney
2026-09-30  9:12   ` Miguel Ojeda
2026-09-30  2:42 ` [PATCH v9 5/9] rust: use Alignment size constants Eliot Courtney
2026-09-30  2:42 ` [PATCH v9 6/9] rust: bitmap: add contiguous area operations Eliot Courtney
2026-09-30  4:41   ` Yury Norov
2026-09-30  2:42 ` [PATCH v9 7/9] rust: id_pool: add contiguous ID reservation Eliot Courtney
2026-09-30  2:51   ` sashiko-bot
2026-09-30  4:50   ` Yury Norov
2026-09-30  2:42 ` [PATCH v9 8/9] rust: id_pool: do not round capacity up to BitmapVec::MAX_INLINE_LEN Eliot Courtney
2026-09-30  2:52   ` sashiko-bot
2026-09-30  5:05   ` Yury Norov
2026-10-01  6:20     ` Alexandre Courbot
2026-10-08 15:47       ` Yury Norov
2026-10-08 16:04         ` Gary Guo
2026-10-09 14:07         ` Alexandre Courbot
2026-09-30  2:42 ` [PATCH v9 9/9] gpu: nova-core: add ChannelIdPool Eliot Courtney
2026-10-08 15:04 ` Alexandre Courbot [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=DLZJSCA10YBI.2NIG6CA24G8L@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=burak.emir@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=ttabi@nvidia.com \
    --cc=work@onurozkan.dev \
    --cc=ynorov@nvidia.com \
    --cc=yury.norov@gmail.com \
    --cc=zhiw@nvidia.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