From: lyude@redhat.com
To: 김범석 <dilddream31@gmail.com>, nouveau@lists.freedesktop.org
Cc: dakr@kernel.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/nouveau: Clear fence channel in no-signaling path
Date: Fri, 23 Oct 2026 13:19:10 -0400 [thread overview]
Message-ID: <939ee9cdaa3a561f5910fde2e4efacc8c92fd39b.camel@redhat.com> (raw)
In-Reply-To: <CAGC3ukSVk=N4ttd3hwnXXXppHchwroJmySPAFP65Vt+uP0COOw@mail.gmail.com>
On Thu, 2026-10-15 at 19:40 +0900, 김범석 wrote:
> Gentle Ping.
>
> There has been some related discussion here:
> https://lore.kernel.org/r/1690ea65-a1e0-4a34-bde1-bdd26e31c6c4@u-bordeaux.fr
>
> The patch has also been independently tested, with no reproduction of
> the issue reported so far.
>
> Apologies if you received this twice. My previous message was
> rejected
> by the mailing list due to HTML formatting.
It's no problem, I'm going to try to get back to reviewing stuff asap -
currently I'm in the middle of moving however so I've got to focus on
higher priority stuff at work at the moment. So it might take me 2 or 3
weeks before I can start reviewing stuff again
>
>
> Thanks.
>
>
> 2026년 10월 15일 (목) 오후 6:10, 김범석 <dilddream31@gmail.com>님이 작성:
> >
> > Gentle Ping.
> >
> > There has been some related discussion here:
> > https://lore.kernel.org/r/1690ea65-a1e0-4a34-bde1-bdd26e31c6c4@u-bordeaux.fr
> >
> > The patch has also been independently tested, with no reproduction
> > of the issue reported so far.
> >
> >
> > Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: lyude@redhat.com
To: 김범석 <dilddream31@gmail.com>, nouveau@lists.freedesktop.org
Cc: dakr@kernel.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/nouveau: Clear fence channel in no-signaling path
Date: Fri, 23 Oct 2026 13:19:10 -0400 [thread overview]
Message-ID: <939ee9cdaa3a561f5910fde2e4efacc8c92fd39b.camel@redhat.com> (raw)
In-Reply-To: <CAGC3ukSVk=N4ttd3hwnXXXppHchwroJmySPAFP65Vt+uP0COOw@mail.gmail.com>
On Thu, 2026-10-15 at 19:40 +0900, 김범석 wrote:
> Gentle Ping.
>
> There has been some related discussion here:
> https://lore.kernel.org/r/1690ea65-a1e0-4a34-bde1-bdd26e31c6c4@u-bordeaux.fr
>
> The patch has also been independently tested, with no reproduction of
> the issue reported so far.
>
> Apologies if you received this twice. My previous message was
> rejected
> by the mailing list due to HTML formatting.
It's no problem, I'm going to try to get back to reviewing stuff asap -
currently I'm in the middle of moving however so I've got to focus on
higher priority stuff at work at the moment. So it might take me 2 or 3
weeks before I can start reviewing stuff again
>
>
> Thanks.
>
>
> 2026년 10월 15일 (목) 오후 6:10, 김범석 <dilddream31@gmail.com>님이 작성:
> >
> > Gentle Ping.
> >
> > There has been some related discussion here:
> > https://lore.kernel.org/r/1690ea65-a1e0-4a34-bde1-bdd26e31c6c4@u-bordeaux.fr
> >
> > The patch has also been independently tested, with no reproduction
> > of the issue reported so far.
> >
> >
> > Thanks.
next prev parent reply other threads:[~2026-10-23 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:14 [PATCH] drm/nouveau: Clear fence channel in no-signaling path Beomseok Kim
2026-09-28 8:14 ` Beomseok Kim
2026-10-15 9:10 ` 김범석
2026-10-15 9:10 ` 김범석
2026-10-15 10:40 ` 김범석
2026-10-15 10:40 ` 김범석
2026-10-23 17:19 ` lyude [this message]
2026-10-23 17:19 ` lyude
2026-11-12 21:40 ` Marek Czernohous
2026-11-12 21:40 ` Marek Czernohous
2026-11-13 13:00 ` Fab Stz
2026-11-13 13:00 ` Fab Stz
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=939ee9cdaa3a561f5910fde2e4efacc8c92fd39b.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dilddream31@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.