[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y1DTFiP12ws04eOM@sol.localdomain>
Date: Wed, 19 Oct 2022 21:48:22 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Hamza Mahfooz <hamza.mahfooz@....com>,
Alex Deucher <alexander.deucher@....com>,
christian.koenig@....com, Xinhui.Pan@....com, airlied@...ux.ie,
daniel@...ll.ch, guchun.chen@....com, aurabindo.pillai@....com,
evan.quan@....com, seanpaul@...omium.org, contact@...rsion.fr,
greenfoo@....eu, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH AUTOSEL 5.19 07/16] drm/amdgpu: use dirty framebuffer
helper
On Wed, Sep 21, 2022 at 11:53:23AM -0400, Sasha Levin wrote:
> From: Hamza Mahfooz <hamza.mahfooz@....com>
>
> [ Upstream commit 66f99628eb24409cb8feb5061f78283c8b65f820 ]
>
> Currently, we aren't handling DRM_IOCTL_MODE_DIRTYFB. So, use
> drm_atomic_helper_dirtyfb() as the dirty callback in the amdgpu_fb_funcs
> struct.
>
> Signed-off-by: Hamza Mahfooz <hamza.mahfooz@....com>
> Acked-by: Alex Deucher <alexander.deucher@....com>
> Signed-off-by: Alex Deucher <alexander.deucher@....com>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
I just spent a long time bisecting a hard-to-reproduce regression to this
commit, only to find that a revert was just queued this week.
Why was this commit backported to stable in the first place? It didn't have Cc
stable, and it didn't claim to be fixing anything.
- Eric
Powered by blists - more mailing lists