From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Lyude Paul <lyude@redhat.com>,
Marek Czernohous <mczernohous@gmail.com>
Subject: Re: [PATCH 6.6.y] drm/nouveau: disable the fence uevent work instead of just cancelling it
Date: Thu, 12 Nov 2026 21:33:26 -0500 [thread overview]
Message-ID: <daily-reply-2026-11-12-120429057@kernel.org> (raw)
In-Reply-To: <179447220252.849346.18231918170218281434@gmail.com>
On 2026-11-12, Marek Czernohous wrote:
> [PATCH 6.6.y] drm/nouveau: disable the fence uevent work instead of just cancelling it
> nouveau_fence_context_del() drains the uevent work while the event that
> feeds it is still armed:
> cancel_work_sync(&fctx->uevent_work);
Queued for 6.6, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-13 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 10:28 FAILED: patch "[PATCH] drm/nouveau: disable the fence uevent work instead of just cancelling it" failed to apply to 6.6-stable tree Sasha Levin
2026-11-12 8:30 ` [PATCH 6.6.y] drm/nouveau: disable the fence uevent work instead of just cancelling it Marek Czernohous
2026-11-13 2:33 ` Sasha Levin [this message]
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=daily-reply-2026-11-12-120429057@kernel.org \
--to=sashal@kernel.org \
--cc=lyude@redhat.com \
--cc=mczernohous@gmail.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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