On Wed, 04 Nov 2026 02:53:40 +0000, Wentao Liang wrote:
> The v5.0.0 software initialization callback creates its ring before
> allocating the register dump storage and creating the reset mask sysfs
> file. If either of the latter steps fails, the callback returns without
> releasing the initialized JPEG resources, including the ring buffers and
> the vmid_wait fence reference. The IP block's status.sw flag has not been
> set, so the common error cleanup skips its sw_fini callback.
>
> Suspend the JPEG work and release the JPEG software resources on these
> late failures. amdgpu_jpeg_sw_fini() also releases the register dump
> storage if it was successfully allocated before sysfs creation failed.
>
> Fixes: 64dc2f0029ec ("drm/amdgpu: Enable devcoredump for JPEG5_0_0")
> Cc: [email protected]
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <[email protected]>
> ---
> drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_0.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
Multiple things here:
1. Your team ignored completely previous feedback. Multiple times.
2. You use multiple identities with this email address, thus I doubt that we
speak with an actual person.
3. Your bot does not even bother running checkpatch, right?
4. Nothing of this was reproduced nor tested.
5. Finally, the same feedback:
You sent multiple independent patches, to multiple independent
subsystems. The amount of these patches clearly suggest this was
AI generated and most likely not tested.
More importantly, you sent all this work without properly organizing
relevant patches into patchsets. This makes reviewing difficult
and might cause multiple reviewers to address the same issue.
Replying to the entire set is impossible and requires handling each
patch independently, instead of applying or discarding the set.
Maintainers also won't see the bigger picture of your work. Quite
worrying.
This is on the verge of hostile patch: bomb us with so many
contributions, we won't be able to handle them in efficient manner,
like responding ONCE to ask you to slow down. Considering all this
is untested and LLM generated, I have even more doubts whether this
should be considered for review.
Please read kernel documentation BEFORE posting more work. It will
explain you how to identify subsystems, how to organize your work per
subsystem (so a patchset grouping multiple patches with a short cover
letter), how to document the issue discovery method and what was
or was not tested.
Best regards,
Krzysztof
