linux-kernel - Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 17 Jun 2024 11:11:08 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: Marek Vasut <marex@...x.de>, 
	Tomi Valkeinen <tomi.valkeinen@...asonboard.com>, Alexander Stein <alexander.stein@...tq-group.com>, 
	Aradhya Bhatia <a-bhatia1@...com>, Andrzej Hajda <andrzej.hajda@...el.com>, 
	Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>, 
	Laurent Pinchart <Laurent.pinchart@...asonboard.com>, Jonas Karlman <jonas@...boo.se>, 
	Jernej Skrabec <jernej.skrabec@...il.com>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, 
	Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, 
	David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>, Sam Ravnborg <sam@...nborg.org>, 
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] drm/bridge: tc358767: Fix
 DRM_BRIDGE_ATTACH_NO_CONNECTOR case

On Mon, Jun 17, 2024 at 07:40:32AM GMT, Jan Kiszka wrote:
> On 16.02.24 15:57, Marek Vasut wrote:
> > On 2/16/24 10:10, Tomi Valkeinen wrote:
> >> Ok. Does anyone have a worry that these patches make the situation
> >> worse for the DSI case than it was before? Afaics, if the DSI lanes
> >> are not set up early enough by the DSI host, the driver would break
> >> with and without these patches.
> >>
> >> These do fix the driver for DRM_BRIDGE_ATTACH_NO_CONNECTOR and DPI, so
> >> I'd like to merge these unless these cause a regression with the DSI
> >> case.
> > 
> > 1/2 looks good to me, go ahead and apply .
> 
> My local patches still apply on top of 6.10-rc4, so I don't think this
> ever happened. What's still holding up this long-pending fix (at least
> for our devices)?

Neither of the patches contains Fixes tags. If the first patch fixes an
issue in previous kernels, please consider following the stable process.

If we are unsure about the second patch, please send the first patch
separately, adding proper tags.

-- 
With best wishes
Dmitry