All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deborah Brouwer <deborah.brouwer@collabora.com>
To: Gary Guo <gary@garyguo.net>
Cc: Danilo Krummrich <dakr@kernel.org>,
	Eliot Courtney <ecourtney@nvidia.com>,
	aliceryhl@google.com, daniel.almeida@collabora.com,
	boris.brezillon@collabora.com, dri-devel@lists.freedesktop.org,
	rust-for-linux@vger.kernel.org,
	dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] gpu: drm: tyr: use IoMem directly instead of Devres
Date: Thu, 28 May 2026 14:51:29 -0700	[thread overview]
Message-ID: <ahi44Zwu29bgxoCc@um790> (raw)
In-Reply-To: <DIUBT4GXKI2Q.3RZEYJVWXZF18@garyguo.net>

On Thu, May 28, 2026 at 01:58:35PM +0100, Gary Guo wrote:
> On Thu May 28, 2026 at 12:31 AM BST, Danilo Krummrich wrote:
> > On Thu May 28, 2026 at 1:03 AM CEST, Deborah Brouwer wrote:
> >> On Tue, May 26, 2026 at 11:43:38AM +0900, Eliot Courtney wrote:
> >>> On Tue May 26, 2026 at 8:01 AM JST, Danilo Krummrich wrote:
> >>> > @@ -40,9 +39,7 @@
> >>> >  pub(crate) struct GpuInfo(pub(crate) uapi::drm_panthor_gpu_info);
> >>> >  
> >>> >  impl GpuInfo {
> >>> > -    pub(crate) fn new(dev: &Device<Bound>, iomem: &Devres<IoMem>) -> Result<Self> {
> >>> > -        let io = (*iomem).access(dev)?;
> >>> > -
> >>> > +    pub(crate) fn new(io: &IoMem<'_>) -> Result<Self> {
> >>> 
> >>> Perhaps a future patch can remove this now unnecessary looking Result in
> >>> the return type.
> >>
> >> Oh that's right now that we don't have: let io = (*iomem).access(dev)?
> >> we don't need the Result anymore.
> >>
> >> Danilo, I can add this fix to our fw-boot series which I'm preparing to sit
> >> on top of these changes.
> >
> > I can send a v2, fix it up on apply when I get an ACK, have Alice fix it up on
> > apply, or have it done in a follow-up as you offer -- just let me know. :)
> >
> 
> I think it makes sense to have a v2 with this, as getting rid of impossible
> failure paths is the reason we go for lifetime in the first place, so this is a
> good demonstration of that benefit.

yeah v2 is probably the cleanest/easiest way to fix.

And while here it would be nice to keep the subject prefix consistent,
we've been using "drm/tyr:"

> 
> Best,
> Gary

  reply	other threads:[~2026-05-28 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 23:01 [PATCH 0/2] drm: tyr: use lifetime-bound IoMem Danilo Krummrich
2026-05-25 23:01 ` [PATCH 1/2] gpu: drm: tyr: separate driver type from driver data Danilo Krummrich
2026-05-26  1:17   ` Eliot Courtney
2026-05-26  6:43   ` Boris Brezillon
2026-05-27 22:56   ` Deborah Brouwer
2026-05-28 12:56   ` Gary Guo
2026-05-25 23:01 ` [PATCH 2/2] gpu: drm: tyr: use IoMem directly instead of Devres Danilo Krummrich
2026-05-26  1:30   ` Alexandre Courbot
2026-05-26  2:43   ` Eliot Courtney
2026-05-27 23:03     ` Deborah Brouwer
2026-05-27 23:31       ` Danilo Krummrich
2026-05-28 12:58         ` Gary Guo
2026-05-28 21:51           ` Deborah Brouwer [this message]
2026-05-27 22:56   ` Deborah Brouwer

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=ahi44Zwu29bgxoCc@um790 \
    --to=deborah.brouwer@collabora.com \
    --cc=aliceryhl@google.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel-bounces@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=rust-for-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.