[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250415121900.55719-2-phasta@kernel.org>
Date: Tue, 15 Apr 2025 14:18:59 +0200
From: Philipp Stanner <phasta@...nel.org>
To: Lyude Paul <lyude@...hat.com>,
Danilo Krummrich <dakr@...nel.org>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Sabrina Dubroca <sd@...asysnail.net>,
Sumit Semwal <sumit.semwal@...aro.org>,
Christian König <christian.koenig@....com>
Cc: dri-devel@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org,
linux-kernel@...r.kernel.org,
netdev@...r.kernel.org,
linux-media@...r.kernel.org,
linaro-mm-sig@...ts.linaro.org,
Philipp Stanner <phasta@...nel.org>
Subject: [PATCH v2 0/2] drm/nouveau: Don't set signaled fences' error codes
Changes in v2:
- Only fix the issue by checking for a fence being signaled in
nouveau_fence_context_kill(), before setting the fence's error.
(Christian, Danilo)
- Drop cleanup patches. Instead, idiomaticize for-each-loops.
Was called "Fix & improve nouveau_fence_done()" before.
I've tested this with KASAN & kmemleak.
P.
Philipp Stanner (2):
drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()
drm/nouveau: nouveau_fence: Standardize list iterations
drivers/gpu/drm/nouveau/nouveau_fence.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.48.1
Powered by blists - more mailing lists