[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200306234923.547873-1-lyude@redhat.com>
Date: Fri, 6 Mar 2020 18:49:20 -0500
From: Lyude Paul <lyude@...hat.com>
To: dri-devel@...ts.freedesktop.org
Cc: "Alex Deucher" <alexander.deucher@....com>,
"Daniel Vetter" <daniel@...ll.ch>,
"Mikita Lipski" <mikita.lipski@....com>,
"David Airlie" <airlied@...ux.ie>,
"David Francis" <david.francis@....com>,
"Maarten Lankhorst" <maarten.lankhorst@...ux.intel.com>,
linux-kernel@...r.kernel.org,
"Harry Wentland" <harry.wentland@....com>,
"Thomas Zimmermann" <tzimmermann@...e.de>,
"Maxime Ripard" <mripard@...nel.org>,
"Lyude Paul" <lyude@...hat.com>,
"Benjamin Gaignard" <benjamin.gaignard@...com>
Subject: [PATCH 0/2] drm/dp_mst: Fix link address probing regressions
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
Powered by blists - more mailing lists