From: Mario Limonciello <mario.limonciello@amd.com>
To: stable@vger.kernel.org
Cc: mjanes@netflix.com, "Deucher, Alexander" <alexander.deucher@amd.com>
Subject: [6.18.y] Missing TLB fix for 6.18.y
Date: Mon, 4 May 2026 14:43:01 -0500 [thread overview]
Message-ID: <04e60ca1-5acd-4c18-aa48-f5650b301137@amd.com> (raw)
Hi,
Mark Janes noticed that commit e9f58ff991dd4 ("drm/amdgpu: rework how we
handle TLB fences") was missing from 6.18.y.
This went into 7.0-rc5 and was backported to 6.19.y but not 6.18.y.
This is because this was one of those cases that the "Fixed" commit was
in both 6.18 and 6.19.y as different hashes:
b4a7f4e7ad2b120a94f3111f92a11520052c762d
f3854e04b708d73276c4488231a8bd66d30b4671
So can you please backport e9f58ff991dd4 to 6.18.y?
Thanks,
next reply other threads:[~2026-05-04 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 19:43 Mario Limonciello [this message]
2026-05-04 19:52 ` [6.18.y] Missing TLB fix for 6.18.y Deucher, Alexander
2026-05-12 17:21 ` Greg KH
2026-05-12 20:53 ` Deucher, Alexander
2026-05-04 19:53 ` Mario Limonciello
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=04e60ca1-5acd-4c18-aa48-f5650b301137@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=mjanes@netflix.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox