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] [day] [month] [year] [list]
Message-ID: <171615394192.98831.12547491683028150051.b4-ty@linaro.org>
Date: Mon, 20 May 2024 00:25:59 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org,
	Liu Ying <victor.liu@....com>
Cc: andrzej.hajda@...el.com,
	neil.armstrong@...aro.org,
	rfoss@...nel.org,
	Laurent.pinchart@...asonboard.com,
	jonas@...boo.se,
	jernej.skrabec@...il.com,
	maarten.lankhorst@...ux.intel.com,
	mripard@...nel.org,
	tzimmermann@...e.de,
	airlied@...il.com,
	daniel@...ll.ch,
	biju.das.jz@...renesas.com,
	aford173@...il.com,
	bli@...g-olufsen.dk,
	robh@...nel.org,
	jani.nikula@...el.com
Subject: Re: [PATCH] drm/bridge: adv7511: Attach next bridge without creating connector

On Mon, 13 May 2024 16:02:43 +0800, Liu Ying wrote:
> The connector is created by either this ADV7511 bridge driver or
> any DRM device driver/previous bridge driver, so this ADV7511
> bridge driver should not let the next bridge driver create connector.
> 
> If the next bridge is a HDMI connector, the next bridge driver
> would fail to attach bridge from display_connector_attach() without
> the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag.
> 
> [...]

Applied to drm-misc-next-fixes, thanks!

[1/1] drm/bridge: adv7511: Attach next bridge without creating connector
      commit: 20da948e3a807c67f0efe4f665e64728be370f3d

Best regards,
-- 
With best wishes
Dmitry


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ