From: Zack Rusin <zack.rusin@broadcom.com>
To: Claire DuSoleil <claire.m.dusoleil@gmail.com>
Cc: "Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH] drm/vmwgfx: Fix GEM_CLOSE returning -EINVAL for PRIME-imported surfaces
Date: Thu, 17 Sep 2026 16:19:23 -0400 [thread overview]
Message-ID: <CABQX2QM6vB3+AaJdSBu_gVN=Mw9Fz5W5xoDR2mxsUKRLaPpOvQ@mail.gmail.com> (raw)
In-Reply-To: <20260917181312.12473-1-claire.m.dusoleil@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Thu, Sep 17, 2026 at 2:13 PM Claire DuSoleil
<claire.m.dusoleil@gmail.com> wrote:
> All seven changed files were also confirmed byte-for-byte
Sure, humans do that all the time... Seriously though, this is crazy.
Claire, you can't expect anyone to even look at this. You just wasted
tokens/compute by letting some LLM run wild. If you want to use an LLM
to help fix the bug you are trying to address, the best approach is to
have it generate IGT testcases so that people who understand the code
and have a running test setup for this driver can tackle it.
z
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5414 bytes --]
next prev parent reply other threads:[~2026-09-17 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 18:13 Claire DuSoleil
2026-09-17 20:19 ` Zack Rusin [this message]
2026-09-18 11:26 ` kernel test robot
2026-09-18 20:56 ` Maaz Mombasawala
[not found] ` <CAEcBvW0+SqM2zHbaDS+JycXxc-ztzvixKtHVSVQby9viVH=+eA@mail.gmail.com>
2026-09-18 21:23 ` Claire DuSoleil
2026-09-18 23:36 ` Maaz Mombasawala
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='CABQX2QM6vB3+AaJdSBu_gVN=Mw9Fz5W5xoDR2mxsUKRLaPpOvQ@mail.gmail.com' \
--to=zack.rusin@broadcom.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=christian.koenig@amd.com \
--cc=claire.m.dusoleil@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.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®