From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Jayesh Choudhary <j-choudhary@ti.com>,
dri-devel@lists.freedesktop.org, sjakhade@cadence.com,
jsarha@ti.com, mripard@kernel.org,
Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
neil.armstrong@linaro.org, rfoss@kernel.org
Cc: amishin@t-argos.ru, jani.nikula@intel.com, tzimmermann@suse.de,
maarten.lankhorst@linux.intel.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, linux-kernel@vger.kernel.org,
devarsht@ti.com, Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [RFC PATCH] drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference
Date: Fri, 24 Jan 2025 09:08:21 +0100 [thread overview]
Message-ID: <9431081.CDJkKcVGEf@steina-w> (raw)
In-Reply-To: <e76f94b9-b138-46e7-bb18-b33dd98c9abb@ideasonboard.com>
Hi,
Am Donnerstag, 23. Januar 2025, 17:20:34 CET schrieb Tomi Valkeinen:
> Hi,
>
> On 16/01/2025 13:16, Jayesh Choudhary wrote:
> > For the cases we have DRM_BRIDGE_ATTACH_NO_CONNECTOR flag set,
>
> Any idea if any other platform than K3 is using this driver? tidss
> supports DRM_BRIDGE_ATTACH_NO_CONNECTOR, so if K3 is the only user, we
> could drop the legacy !DRM_BRIDGE_ATTACH_NO_CONNECTOR case. Which would
> remove quite a bit of code, I think, and make the driver a bit more easy
> to understand (although I think it could use a major cleanup...).
FYI: Not directly using it, but patch series [1] is at least touching
this file.
Best regards,
Alexander
[1] https://lore.kernel.org/all/cover.1734340233.git.Sandor.yu@nxp.com/
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2025-01-24 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 11:16 [RFC PATCH] drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference Jayesh Choudhary
2025-01-23 16:20 ` Tomi Valkeinen
2025-01-24 8:08 ` Alexander Stein [this message]
2025-01-28 5:57 ` Jayesh Choudhary
2025-05-21 7:36 ` Jayesh Choudhary
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=9431081.CDJkKcVGEf@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=amishin@t-argos.ru \
--cc=andrzej.hajda@intel.com \
--cc=devarsht@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j-choudhary@ti.com \
--cc=jani.nikula@intel.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=jsarha@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.