From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Francesco Dolcini" <francesco@dolcini.it>,
<max.oss.09@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Neil Armstrong" <neil.armstrong@linaro.org>
Cc: "Adrien Grassein" <adrien.grassein@gmail.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Robert Foss" <rfoss@kernel.org>,
"Simona Vetter" <simona@ffwll.ch>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/bridge: lontium-lt8912b: Do not generate HFP
Date: Thu, 30 Apr 2026 09:53:08 +0200 [thread overview]
Message-ID: <DI6BS0B8HTLP.2Q00QFIUQUZRU@bootlin.com> (raw)
In-Reply-To: <20260429133333.GA68737@francesco-nb>
Hi Francesco,
On Wed Apr 29, 2026 at 3:33 PM CEST, Francesco Dolcini wrote:
> +Dmitry, Luca
>
> Hello all,
> how to get this patch considered and eventually merged? I see that this
> is not moving since long.
>
> Considering that Adrien Grassein is not visible on the mailing list
> since 2022, and that I have various HW available that is using this
> combination (on TI Sitara and Jacinto, on a DPI-DSI tc358768 bridge,
> and NXP i.MX), I have access to the (little) documentation that is
> available from Lontium I can propose myself as a maintainer here.
Thanks for volunteering! I am not a DRM maintainer, so I'll let others
chime in, but I suspect you should just send a patch to add yourself to the
MAINTAINERS entry and (as a separate patch?) remove Adrien, unless he
speaks up by then.
> I assume being able to ack patches would help the maintenance here, or
> is this just a glitch and a ping was enough?
dri-devel is flooded by patches, driver-specific ones will unavoidably be
missed in lack of a responsive maintainer. So this is not a glitch, it's a
frequent pattern I'm afraid.
As above, if you were in the MAINTAINERS entry, look at patches and comment
on them, and test on hardware that would be great IMHO.
For this one patch: it looks OK.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Adding the "why" would be better, which I assume to be power saving. No
need to sned a v2 just for that though.
I'm applying it in ~1 week. It would be good if you could check it still
applies on drm-misc-next before that, report back if it does, send a v2
(adding the "why") if it doesn't.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-04-30 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:00 [PATCH] drm/bridge: lontium-lt8912b: Do not generate HFP max.oss.09
2025-09-11 15:34 ` Francesco Dolcini
2025-10-27 10:14 ` Max Krummenacher
2026-04-29 13:33 ` Francesco Dolcini
2026-04-30 7:53 ` Luca Ceresoli [this message]
2026-04-30 8:05 ` Adrien Grassein
2026-04-30 8:15 ` Francesco Dolcini
2026-05-04 10:41 ` Luca Ceresoli
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=DI6BS0B8HTLP.2Q00QFIUQUZRU@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=adrien.grassein@gmail.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francesco@dolcini.it \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=max.oss.09@gmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox