From: Philipp Stanner <phasta@kernel•org>
To: "Lyude Paul" <lyude@redhat•com>,
"Danilo Krummrich" <dakr@kernel•org>,
"David Airlie" <airlied@gmail•com>,
"Simona Vetter" <simona@ffwll•ch>,
"Sabrina Dubroca" <sd@queasysnail•net>,
"Sumit Semwal" <sumit.semwal@linaro•org>,
"Christian König" <christian.koenig@amd•com>
Cc: dri-devel@lists•freedesktop.org, nouveau@lists•freedesktop.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
linux-media@vger•kernel.org, linaro-mm-sig@lists•linaro.org,
Philipp Stanner <phasta@kernel•org>
Subject: [PATCH v2 0/2] drm/nouveau: Don't set signaled fences' error codes
Date: Tue, 15 Apr 2025 14:18:59 +0200 [thread overview]
Message-ID: <20250415121900.55719-2-phasta@kernel.org> (raw)
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
next reply other threads:[~2025-04-15 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:18 Philipp Stanner [this message]
2025-04-15 12:19 ` [PATCH v2 1/2] drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill() Philipp Stanner
2025-04-23 15:54 ` Danilo Krummrich
2025-04-15 12:19 ` [PATCH v2 2/2] drm/nouveau: nouveau_fence: Standardize list iterations Philipp Stanner
2025-04-15 12:28 ` Christian König
2025-04-23 15:26 ` Danilo Krummrich
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=20250415121900.55719-2-phasta@kernel.org \
--to=phasta@kernel$(echo .)org \
--cc=airlied@gmail$(echo .)com \
--cc=christian.koenig@amd$(echo .)com \
--cc=dakr@kernel$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linaro-mm-sig@lists$(echo .)linaro.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=lyude@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nouveau@lists$(echo .)freedesktop.org \
--cc=sd@queasysnail$(echo .)net \
--cc=simona@ffwll$(echo .)ch \
--cc=sumit.semwal@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox