From: sashiko-bot@kernel.org
To: "Alex Deucher" <alexander.deucher@amd.com>,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] Revert "drm/amdgpu: reemit RLC SPM register in ring reemit"
Date: Fri, 13 Nov 2026 15:55:41 +0000 [thread overview]
Message-ID: <sashiko-outbox-213131@kernel.org> (raw)
In-Reply-To: <20261113154954.1865439-2-alexander.deucher@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/amdgpu: missing Fixes trailer on revert of commit
8a4dfdc0d2ad
--
commit 765981743becaf8dc015c14e1e583ccf6339298b
Author: Alex Deucher <alexander.deucher@amd.com>
> Revert "drm/amdgpu: reemit RLC SPM register in ring reemit"
>
> This reverts commit 8a4dfdc0d2adfc362ec310ff70526e79ff8377b6.
>
> This causes flakiness in gfx11 CI tests. Revert.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
[Severity: Low]
Since this reverts a commit to fix gfx11 CI flakiness, should the commit
message include a Fixes tag so stable and backport tooling pairs it with
the offending commit?
Fixes: 8a4dfdc0d2ad ("drm/amdgpu: reemit RLC SPM register in ring reemit")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113154954.1865439-1-alexander.deucher@amd.com?part=2
next prev parent reply other threads:[~2026-11-13 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 15:49 [PATCH 1/3] Revert "drm/amdgpu: re-enable SPM updates in the the IB path" Alex Deucher
2026-11-13 15:49 ` [PATCH 2/3] Revert "drm/amdgpu: reemit RLC SPM register in ring reemit" Alex Deucher
2026-11-13 15:55 ` sashiko-bot [this message]
2026-11-13 15:49 ` [PATCH 3/3] drm/amdgpu: bring back the ring parameter for update_spm_vmid() Alex Deucher
2026-11-13 16:15 ` sashiko-bot
2026-11-13 15:58 ` [PATCH 1/3] Revert "drm/amdgpu: re-enable SPM updates in the the IB path" sashiko-bot
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=sashiko-outbox-213131@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.