From: Alex Deucher <alexander.deucher@amd.com>
To: <amd-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <airlied@gmail.com>,
<daniel.vetter@ffwll.ch>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] amdgpu drm-fixes-5.15
Date: Wed, 27 Oct 2021 22:31:30 -0400 [thread overview]
Message-ID: <20211028023130.4528-1-alexander.deucher@amd.com> (raw)
Hi Dave, Daniel,
Fixes for 5.15.
The following changes since commit defbbcd99fa68cb7feed453662048baa87e9a441:
Merge tag 'amd-drm-fixes-5.15-2021-10-21' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes (2021-10-27 10:01:21 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-5.15-2021-10-27
for you to fetch changes up to ad76744b041d8c87ef1c9adbb04fb7eaa20a179e:
drm/amd/display: Fix deadlock when falling back to v2 from v3 (2021-10-27 22:04:50 -0400)
----------------------------------------------------------------
amd-drm-fixes-5.15-2021-10-27:
amdgpu:
- Display fixes for DCN 3.1
- Fix potential out of bounds write in debugfs
----------------------------------------------------------------
Michael Strauss (1):
drm/amd/display: Fallback to clocks which meet requested voltage on DCN31
Nicholas Kazlauskas (1):
drm/amd/display: Fix deadlock when falling back to v2 from v3
Patrik Jakobsson (1):
drm/amdgpu: Fix even more out of bound writes from debugfs
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 18 +++++++++---------
.../drm/amd/display/dc/clk_mgr/dcn31/dcn31_clk_mgr.c | 13 ++++++++++---
drivers/gpu/drm/amd/display/modules/hdcp/hdcp_psp.c | 6 ++----
3 files changed, 21 insertions(+), 16 deletions(-)
next reply other threads:[~2021-10-28 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 2:31 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-21 20:34 [pull] amdgpu drm-fixes-5.15 Alex Deucher
2021-09-30 2:30 Alex Deucher
2021-10-01 15:03 ` Daniel Vetter
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=20211028023130.4528-1-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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.