From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: 6.1 amdgpu backports
Date: Sun, 16 Jul 2023 20:20:11 -0500 [thread overview]
Message-ID: <e593a25b-175c-89f8-d178-095bcddddaea@amd.com> (raw)
Hi,
As a follow up to
https://lore.kernel.org/stable/2023071654-flattery-fidgety-0e31@gregkh/
I've sorted out the parts of this series that make sense for 6.1.y.
Here are the ones that come back as clean patches you can directly queue
up to 6.1.y
fd2198727446 ("drm/amd/pm: revise the ASPM settings for thunderbolt
attached scenario")
ef5fca9f7294 ("drm/amdgpu: add the fan abnormal detection feature")
abd51738fe75 ("drm/amdgpu: Fix minmax warning")
2da0036ea99b ("drm/amd/pm: add abnormal fan detection for smu 13.0.0")
570b295248b0 ("drm/amdgpu: fix number of fence calculations")
Any others that need manual fix up will be sent separately.
Thanks,
next reply other threads:[~2023-07-17 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 1:20 Limonciello, Mario [this message]
2023-07-20 18:20 ` 6.1 amdgpu backports Greg KH
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=e593a25b-175c-89f8-d178-095bcddddaea@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.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