From: Lyude Paul <lyude@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Mikita Lipski" <mikita.lipski@amd.com>,
"David Airlie" <airlied@linux.ie>,
"David Francis" <david.francis@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
linux-kernel@vger.kernel.org,
"Harry Wentland" <harry.wentland@amd.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maxime Ripard" <mripard@kernel.org>,
"Lyude Paul" <lyude@redhat.com>,
"Benjamin Gaignard" <benjamin.gaignard@st.com>
Subject: [PATCH 0/2] drm/dp_mst: Fix link address probing regressions
Date: Fri, 6 Mar 2020 18:49:20 -0500 [thread overview]
Message-ID: <20200306234923.547873-1-lyude@redhat.com> (raw)
While fixing some regressions caused by introducing bandwidth checking
into the DP MST atomic helpers, I realized there was another much more
subtle regression that got introduced by a seemingly harmless patch to
fix unused variable errors while compiling with W=1 (mentioned in patch
2). Basically, this regression makes it so sometimes link address
appears to "hang". This patch series fixes it.
Lyude Paul (2):
drm/dp_mst: Make drm_dp_mst_dpcd_write() consistent with
drm_dp_dpcd_write()
drm/dp_mst: Fix drm_dp_check_mstb_guid() return code
drivers/gpu/drm/drm_dp_mst_topology.c | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)
--
2.24.1
next reply other threads:[~2020-03-06 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 23:49 Lyude Paul [this message]
2020-03-06 23:49 ` [PATCH 1/2] drm/dp_mst: Make drm_dp_mst_dpcd_write() consistent with drm_dp_dpcd_write() Lyude Paul
2020-03-06 23:49 ` [PATCH 2/2] drm/dp_mst: Fix drm_dp_check_mstb_guid() return code Lyude Paul
2020-03-09 21:04 ` [PATCH 0/2] drm/dp_mst: Fix link address probing regressions Alex Deucher
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=20200306234923.547873-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=benjamin.gaignard@st.com \
--cc=daniel@ffwll.ch \
--cc=david.francis@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mikita.lipski@amd.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®