public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Joel Fernandes" <joelagnelf@nvidia.com>
Cc: "John Hubbard" <jhubbard@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Timur Tabi" <ttabi@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Eliot Courtney" <ecourtney@nvidia.com>,
	"Shashank Sharma" <shashanks@nvidia.com>,
	"Zhi Wang" <zhiw@nvidia.com>, "David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"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>,
	rust-for-linux@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] gpu: nova-core: use SizeConstants trait for u64 size constants
Date: Thu, 02 Apr 2026 23:55:15 +0900	[thread overview]
Message-ID: <DHIR7Y4FLM2H.ENO8SJ92Q24J@nvidia.com> (raw)
In-Reply-To: <b1c23169-9368-4ec5-98f9-f73fe8128305@nvidia.com>

On Thu Apr 2, 2026 at 11:33 PM JST, Joel Fernandes wrote:
>
>
> On 4/1/2026 6:27 PM, John Hubbard wrote:
>> Replace manual usize-to-u64 conversions of SZ_* constants with the
>> SizeConstants trait's associated constants on u64. With the
>> SizeConstants trait in scope, u64::SZ_1M replaces usize_as_u64(SZ_1M)
>> and similar.
>> 
>> This removes several now-unused imports: usize_as_u64, FromSafeCast,
>> and individual SZ_* type-level constants.
>> 
>> Reviewed-by: Eliot Courtney <ecourtney@nvidia.com>
>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>
> Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
>
> I am very happy to see this series since I have these issues with mm
> patches quite a bit, which this series will resolve. Should I update the
> nova mm series to use these, or wait for it to be merged? The issue with
> updating the nova mm series is, then I'll have to either:
>
>  a) carry the series as a dependency.
>  b) wait for it to merge into drm-rust-next and rebase
>
> I could do a) and add a [REFERENCE] prefix to the patches, similar to how I
> did for some drm buddy bindings patches. Thoughts?

There is no need to carry the series into yours, just add a link to the
cover letter to your dependencies and folks can pick them up.

b4 also provides a dependency management mechanism, and will even fetch
them automatically if the people applying your series also use it.

I don't know which tree is going to pick this series, so whether we can
use it this cycle or not will depend on that. But if it lands in
`drm-rust-next`, then it's just a few weeks until you can drop the
dependency link from your cover letter anyway.

  reply	other threads:[~2026-04-02 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 22:27 [PATCH v4 0/2] rust, nova-core: add DeviceSize trait for SZ_* constants John Hubbard
2026-04-01 22:27 ` [PATCH v4 1/2] rust: sizes: add SizeConstants trait for device address space constants John Hubbard
2026-04-02 14:43   ` Alexandre Courbot
2026-04-01 22:27 ` [PATCH v4 2/2] gpu: nova-core: use SizeConstants trait for u64 size constants John Hubbard
2026-04-02 14:33   ` Joel Fernandes
2026-04-02 14:55     ` Alexandre Courbot [this message]
2026-04-02 14:59       ` Joel Fernandes
2026-04-02 15:05         ` Joel Fernandes
2026-04-02 15:23           ` Alexandre Courbot
2026-04-02 14:39 ` [PATCH v4 0/2] rust, nova-core: add DeviceSize trait for SZ_* constants Gary Guo

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=DHIR7Y4FLM2H.ENO8SJ92Q24J@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=ecourtney@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=shashanks@nvidia.com \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --cc=ttabi@nvidia.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