From: "Eliot Courtney" <ecourtney@nvidia.com>
To: "Danilo Krummrich" <dakr@kernel.org>, "Gary Guo" <gary@garyguo.net>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Lyude Paul" <lyude@redhat.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>, <rust-for-linux@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] gpu: nova-core: bitfield: fix broken Default implementation
Date: Thu, 02 Apr 2026 10:02:58 +0900 [thread overview]
Message-ID: <DHI9IPJEWW6Y.J0ZNXAS9T7AV@nvidia.com> (raw)
In-Reply-To: <96e7ec53-9b98-4203-a011-77241c95ac88@kernel.org>
On Thu Apr 2, 2026 at 12:44 AM JST, Danilo Krummrich wrote:
> On 4/1/26 5:35 PM, Gary Guo wrote:
>> This could go via drm-rust-fixes?
>
> It seems there's nothing actually broken due to that, so no need to take it
> through -fixes. But we can pick it up before drm-rust-next opens for new
> features as I will send another -next PR for the unsoundness fix anyways.
Yes, nothing actually broken from this right now.
Thanks all
next prev parent reply other threads:[~2026-04-02 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 1:42 [PATCH v2] gpu: nova-core: bitfield: fix broken Default implementation Eliot Courtney
2026-04-01 4:26 ` Alexandre Courbot
2026-04-01 15:35 ` Gary Guo
2026-04-01 15:44 ` Danilo Krummrich
2026-04-02 1:02 ` Eliot Courtney [this message]
2026-04-03 17:37 ` Danilo Krummrich
2026-04-04 0:09 ` Danilo Krummrich
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=DHI9IPJEWW6Y.J0ZNXAS9T7AV@nvidia.com \
--to=ecourtney@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@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