[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUUXlOh0rKcynrPZ@zacax395.localdomain>
Date: Sat, 18 Sep 2021 00:32:52 +0200
From: Fernando Ramos <greenfoo@....eu>
To: Sean Paul <sean@...rly.run>
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
freedreno@...ts.freedesktop.org, nouveau@...ts.freedesktop.org,
linux-renesas-soc@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH 08/15] drm/radeon: cleanup: drm_modeset_lock_all() -->
DRM_MODESET_LOCK_ALL_BEGIN()
> > + struct drm_modeset_acquire_ctx ctx;
> > int i, r;
> > + int ret;
>
> Could you please tuck this up with i & r?
Done!
> > - drm_modeset_unlock_all(dev);
> > + DRM_MODESET_LOCK_ALL_END(dev, ctx, ret);
>
> You should check ret here
Would it be save to return at this point if the lock fails?
In other words, can I just add this? --> "if (ret) return ret;"
> > + struct drm_modeset_acquire_ctx ctx;
> > int r;
> > + int ret;
>
> Same suggestion here, move up with r
Done!
> > - drm_modeset_unlock_all(dev);
> > + DRM_MODESET_LOCK_ALL_END(dev, ctx, ret);
>
> Also check ret here
Same question. Would "if (ret) return ret;" be safe here?
> > int i;
> > + int ret;
>
> Move up with i
Done!
> > - drm_modeset_unlock_all(dev);
> > + DRM_MODESET_LOCK_ALL_END(dev, ctx, ret);
> > return 0;
I can also "return ret;" instead of "0".
What happens when a DEFINE_SHOW_ATTRIBUTE'd function returns non-zero? Is it ok?
Or do we want to always return "0" to print whatever we can?
Powered by blists - more mailing lists