From: Maxime Ripard <mripard@kernel.org>
To: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Sunyun Yang <syyang@lontium.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Mohit Dsor <mdsor@qti.qualcomm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
venkata.valluru@oss.qualcomm.com,
Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH v2] drm/bridge: lt9611c: use drm_atomic_commit in callbacks
Date: Tue, 7 Jul 2026 14:35:50 +0200 [thread overview]
Message-ID: <20260707-masterful-hound-from-camelot-46ffca@penduick> (raw)
In-Reply-To: <20260707-lt9611c-v7-v2-1-67d4f688b68d@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hi,
On Tue, Jul 07, 2026 at 01:48:35PM +0530, Mohit Dsor wrote:
> DRM bridge atomic callbacks now pass struct drm_atomic_commit, and
> the atomic helper functions also expect that type. The lt9611c
> driver still declares its callbacks with struct drm_atomic_state,
> which makes the callback assignments and helper calls fail to build
> with incompatible pointer type errors.
>
> Update the lt9611c callback signatures to match the current DRM
> bridge API.
>
> This will fix compilation issue in v7.2.rc1.
>
> Fixes: 96d1cfec419e ("drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver")
> Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
This commit, or driver, doesn't exist in 7.2-rc1.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
prev parent reply other threads:[~2026-07-07 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:18 Mohit Dsor
2026-07-07 12:35 ` Maxime Ripard [this message]
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=20260707-masterful-hound-from-camelot-46ffca@penduick \
--to=mripard@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jesszhan0024@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mdsor@qti.qualcomm.com \
--cc=mohit.dsor@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=syyang@lontium.com \
--cc=tzimmermann@suse.de \
--cc=venkata.valluru@oss.qualcomm.com \
/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®