From: Harry Wentland <harry.wentland@amd.com>
To: Didier 'OdyX' Raboud <odyx@debian.org>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: stable@vger.kernel.org, stanislav.lisovskiy@intel.com,
jerry.zuo@amd.com, bskeggs@redhat.com, Wayne.Lin@amd.com,
mario.limonciello@amd.com
Subject: Re: [PATCH 0/7] Fix MST on amdgpu
Date: Mon, 23 Jan 2023 12:03:31 -0500 [thread overview]
Message-ID: <2f37b537-5ce9-ff5c-d577-24d6ac6b5efe@amd.com> (raw)
In-Reply-To: <4499220.LvFx2qVVIh@turnagra>
On 1/22/23 14:12, Didier 'OdyX' Raboud wrote:
> For the whole series, as rebased on v6.1.7. Tested on this Thinkpad X13 AMD
> Gen2:
>
> Tested-By: Didier Raboud <odyx@debian.org>
Thanks.
Harry
>
> Le vendredi, 20 janvier 2023, 00.51:53 h CET Harry Wentland a écrit :
>> MST has been broken on amdgpu after a refactor in drm_dp_mst
>> code that was aligning drm_dp_mst more closely with the atomic
>> model.
>>
>> The gitlab issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2171
>>
>> This series fixes it.
>
>
prev parent reply other threads:[~2023-01-23 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 23:51 [PATCH 0/7] Fix MST on amdgpu Harry Wentland
2023-01-19 23:51 ` [PATCH 1/7] drm/amdgpu/display/mst: Fix mst_state->pbn_div and slot count assignments Harry Wentland
2023-01-19 23:51 ` [PATCH 2/7] drm/amdgpu/display/mst: limit payload to be updated one by one Harry Wentland
2023-01-19 23:51 ` [PATCH 3/7] drm/amdgpu/display/mst: update mst_mgr relevant variable when long HPD Harry Wentland
2023-01-19 23:51 ` [PATCH 4/7] drm/drm_print: correct format problem Harry Wentland
2023-01-19 23:51 ` [PATCH 5/7] drm/display/dp_mst: Correct the kref of port Harry Wentland
2023-01-19 23:51 ` [PATCH 6/7] drm/amdgpu/display/mst: adjust the naming of mst_port and port of aconnector Harry Wentland
2023-01-19 23:52 ` [PATCH 7/7] drm/amdgpu/display/mst: adjust the logic in 2nd phase of updating payload Harry Wentland
2023-01-20 23:15 ` [PATCH 0/7] Fix MST on amdgpu Lyude Paul
2023-01-23 17:03 ` Harry Wentland
2023-01-22 19:12 ` Didier 'OdyX' Raboud
2023-01-23 17:03 ` Harry Wentland [this message]
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=2f37b537-5ce9-ff5c-d577-24d6ac6b5efe@amd.com \
--to=harry.wentland@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jerry.zuo@amd.com \
--cc=mario.limonciello@amd.com \
--cc=odyx@debian.org \
--cc=stable@vger.kernel.org \
--cc=stanislav.lisovskiy@intel.com \
/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