From: Ruben Wauters <rubenru09@aol.com>
To: Shenghao Yang <me@shenghaoyang.info>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/gud: fix NULL fb and crtc dereferences on USB disconnect
Date: Tue, 13 Jan 2026 14:05:35 +0000 [thread overview]
Message-ID: <69a714228f562d399e78cd0e54a23769490336f9.camel@aol.com> (raw)
In-Reply-To: <65110c51-1f47-4382-ac92-518c7f157a06@shenghaoyang.info>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Thu, 2026-01-08 at 21:39 +0800, Shenghao Yang wrote
Hi
> Hi Ruben, Thomas,
>
> On 7/1/26 23:56, Thomas Zimmermann wrote:
>
> >
> > No worries, DRM semantics can be murky. This is one of the cases that is impossible to know unless you came across a patch like this one.
> >
> > Best regards
> > Thomas
> >
> > > > I think the patch is fine and IIRC we have similar logic in other drivers.
> > > Reviewed-by: Ruben Wauters <rubenru09@aol.com>
Patch applied to drm-misc-fixes, thanks
> > >
> > > I believe Shenghao mentioned another oops that is present? if so it may
> > > be best to submit that in a separate patch rather than a v2 of this
> > > one.
> > >
> > > Ruben
>
>
> Thanks both! I'll split the patch for the second oops.
>
> Shenghao
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
prev parent reply other threads:[~2026-01-13 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 5:50 Shenghao Yang
2026-01-03 17:23 ` Ruben Wauters
2026-01-03 17:47 ` Shenghao Yang
2026-01-03 19:18 ` Ruben Wauters
2026-01-04 16:30 ` Shenghao Yang
2026-01-07 7:46 ` Thomas Zimmermann
2026-01-07 15:02 ` Ruben Wauters
2026-01-07 15:56 ` Thomas Zimmermann
2026-01-08 13:39 ` Shenghao Yang
2026-01-13 14:05 ` Ruben Wauters [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=69a714228f562d399e78cd0e54a23769490336f9.camel@aol.com \
--to=rubenru09@aol.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@shenghaoyang.info \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®