From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: <sashiko-reviews@lists.linux.dev>,
"Alexandre Courbot" <acourbot@nvidia.com>, <ojeda@kernel.org>,
<dri-devel@lists.freedesktop.org>,
"rust-for-linux" <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH 2/7] rust: drm: gem: gate open/close callbacks with RegistrationGuard
Date: Mon, 12 Oct 2026 18:12:31 +0200 [thread overview]
Message-ID: <DM2ZQ8WLXOLQ.Z4U2APODVLL1@kernel.org> (raw)
In-Reply-To: <0CA5ABE5-C198-45D5-B393-50AA219D6F14@collabora.com>
On Mon Oct 12, 2026 at 6:06 PM CEST, Daniel Almeida wrote:
> So you’re saying that close() can be removed entirely? Or did I misunderstand?
Not entirely, it can still be useful when the driver remains bound and the DRM
device registered as an optimization to release resources early. It's just not
useful on / after DRM device unregistration / driver unbind as it implies that
those resources are released anyway.
next prev parent reply other threads:[~2026-10-12 16:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 23:08 [PATCH 0/7] lifetime-parameterized DRM File private data Danilo Krummrich
2026-08-14 23:08 ` [PATCH 1/7] rust: drm: rename Ioctl device context to Userspace Danilo Krummrich
2026-10-09 16:55 ` Daniel Almeida
2026-08-14 23:09 ` [PATCH 2/7] rust: drm: gem: gate open/close callbacks with RegistrationGuard Danilo Krummrich
2026-08-14 23:21 ` sashiko-bot
2026-10-09 17:39 ` Daniel Almeida
2026-10-11 14:15 ` Danilo Krummrich
2026-10-12 16:06 ` Daniel Almeida
2026-10-12 16:12 ` Danilo Krummrich [this message]
2026-10-13 14:03 ` Daniel Almeida
2026-08-14 23:09 ` [PATCH 3/7] rust: drm: move file_operations from gem to device Danilo Krummrich
2026-08-14 23:22 ` sashiko-bot
2026-10-09 17:42 ` Daniel Almeida
2026-08-14 23:09 ` [PATCH 4/7] rust: fs: add iminor() helper Danilo Krummrich
2026-10-09 17:43 ` Daniel Almeida
2026-08-14 23:09 ` [PATCH 5/7] rust: drm: wrap fops open with RegistrationGuard Danilo Krummrich
2026-08-14 23:29 ` sashiko-bot
2026-10-09 18:07 ` Daniel Almeida
2026-08-14 23:09 ` [PATCH 6/7] rust: drm: make Driver::File lifetime-parameterized Danilo Krummrich
2026-08-14 23:23 ` sashiko-bot
2026-08-14 23:09 ` [PATCH 7/7] rust: drm: return impl PinInit from DriverFile::open() 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=DM2ZQ8WLXOLQ.Z4U2APODVLL1@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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