From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: phasta@kernel.org, "cao, lin" <lin.cao@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "Yin, ZhenGuo (Chris)" <ZhenGuo.Yin@amd.com>,
"Deng, Emily" <Emily.Deng@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"matthew.brost@intel.com" <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/sched: Remove optimization that causes hang when killing dependent jobs
Date: Wed, 16 Jul 2025 12:40:35 +0200 [thread overview]
Message-ID: <fd46ca0c-e484-4bf8-b74e-0139ecc7deae@mailbox.org> (raw)
In-Reply-To: <df5fe40e79db8e988661704ea4f72be1a2e4c14c.camel@mailbox.org>
On 16.07.25 11:57, Philipp Stanner wrote:
> On Wed, 2025-07-16 at 09:43 +0000, cao, lin wrote:
>>
>> Hi Philipp,
>>
>>
>> Thank you for the review. I found that this optimization was
>> introduced 9 years ago in commit
>> 777dbd458c89d4ca74a659f85ffb5bc817f29a35 ("drm/amdgpu: drop a dummy
>> wakeup scheduler").
>>
>>
>> Given that the codebase has undergone significant changes over these
>> 9 years. May I ask if I still need to include the Fixes: tag?
>
> Yes. It's a helpful marker to see where the problem comes from, and it
> adds redundancy helping the stable-kernel maintainers in figuring out
> to which kernels to backport it to.
>
> If stable can't apply a patch to a very old stable kernel because the
> code base changed too much, they'll ping us and we might provide a
> dedicated fix.
>
> So like that:
>
> Cc: stable@vger.kernel.org # v4.6+
> Fixes: 777dbd458c89 ("drm/amdgpu: drop a dummy wakeup scheduler")
FWIW, Fixes: alone is enough for getting backported to stable branches, Cc: stable is redundant with it.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2025-07-16 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:50 [PATCH] drm/sched: Remove optimization that causes hang when killing dependent jobs Lin.Cao
2025-07-15 15:42 ` Christian König
2025-07-16 8:33 ` Philipp Stanner
2025-07-16 9:43 ` cao, lin
2025-07-16 9:53 ` Christian König
2025-07-16 9:57 ` Philipp Stanner
2025-07-16 10:05 ` cao, lin
2025-07-16 10:13 ` Danilo Krummrich
2025-07-16 10:46 ` Christian König
2025-07-16 10:40 ` Michel Dänzer [this message]
2025-07-16 10:46 ` Philipp Stanner
2025-07-16 10:58 ` Christian König
2025-07-16 11:15 ` Greg Kroah-Hartman
2025-07-16 11:32 ` Philipp Stanner
2025-07-16 12:05 ` Greg Kroah-Hartman
2025-07-16 14:11 ` Philipp Stanner
2025-07-16 14:24 ` Greg Kroah-Hartman
2025-07-16 11:16 ` Greg Kroah-Hartman
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=fd46ca0c-e484-4bf8-b74e-0139ecc7deae@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=Christian.Koenig@amd.com \
--cc=Emily.Deng@amd.com \
--cc=ZhenGuo.Yin@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lin.cao@amd.com \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
/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.