mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lyude@redhat.com
To: Kush Chandak <kushc451@gmail.com>, Risto Pajula <or.pajula@gmail.com>
Cc: Danilo Krummrich <dakr@kernel.org>,
	nouveau@lists.freedesktop.org,  dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/nouveau: fix GK107 VDPAU regressions
Date: Fri, 23 Oct 2026 13:13:02 -0400	[thread overview]
Message-ID: <8a025f783533d40c0486a8a511e8811b0e52f466.camel@redhat.com> (raw)
In-Reply-To: <20261022153712.11208-1-kushc451@gmail.com>

I am going to look at this patch when I have a moment, but I am in the
middle of moving right now so it's likely going to take me a bit,
however:

On Thu, 2026-10-22 at 21:07 +0530, Kush Chandak wrote:
> On Sun, 13 Sep 2026 23:12:23 +0300, Risto Pajula wrote:
> > This series fixes two independent Nouveau regressions affecting
> > VDPAU
> > hardware video decoding on NVIDIA GK107 (Kepler).
> 
> Tested-by: Kush Chandak <kushc451@gmail.com>
> 
> I used an AI assistant (Claude) to help debug and test this.

Please don't clog up the mailing list with this. I have seen multiple
people now going through and 'testing' things with LLMs, and the
reality is I'm not going to carry across the tested tags.

If you would like to test, there are plenty of resources available to
figure out how to build a kernel against a patch on a mailing list to
test changes. LLMs frequently hallucinate and lack an understanding of
the tasks they perform. It's already difficult enough keeping up with
code submissions, and given that you cannot use LLM output without both
vetting it, and having the knowledge required to properly vet it, there
really is nothing I can actually establish from "testing" like this. If
you weren't able to actually test without using an LLM and we have
established we can't trust the output of the LLM - how am I supposed to
know it was tested? I can't verify it from what you gave me, and even
if I could - that's just doing what is way too commonplace with these
tools and offloading the work of verifying anything that it spits to
others.


      reply	other threads:[~2026-10-23 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 20:12 Risto Pajula
2026-09-13 20:12 ` [PATCH 1/2] drm/nouveau/fifo/gk104: fix legacy video engine context mappings Risto Pajula
2026-09-13 20:12 ` [PATCH 2/2] drm/nouveau/fifo: use global nonstall event on legacy FIFO Risto Pajula
2026-10-22 15:37 ` [PATCH 0/2] drm/nouveau: fix GK107 VDPAU regressions Kush Chandak
2026-10-23 17:13   ` lyude [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=8a025f783533d40c0486a8a511e8811b0e52f466.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kushc451@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=or.pajula@gmail.com \
    /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®