[<prev] [next>] [day] [month] [year] [list]
Message-Id: <166963342298.56696.16356568683060608437.b4-ty@cerno.tech>
Date: Mon, 28 Nov 2022 12:05:01 +0100
From: Maxime Ripard <maxime@...no.tech>
To: Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <maxime@...no.tech>,
Maxime Ripard <mripard@...nel.org>
Cc: dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org,
Javier Martinez Canillas <javierm@...hat.com>,
David Gow <davidgow@...gle.com>, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org,
Ma��ra Canal <mairacanal@...eup.net>,
linux-kselftest@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Brendan Higgins <brendan.higgins@...ux.dev>,
kunit-dev@...glegroups.com,
Dave Stevenson <dave.stevenson@...pberrypi.com>
Subject: Re: (subset) [PATCH 20/24] drm/vc4: crtc: Provide a CRTC name
On Wed, 23 Nov 2022 16:26:02 +0100, Maxime Ripard wrote:
> It's fairly hard to figure out the instance of the CRTC affected by an
> atomic change using the default name.
>
> Since we can provide our own to the CRTC initialization functions, let's
> do so to make the debugging sessions easier.
>
>
> [...]
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
Powered by blists - more mailing lists