Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Sandy Huang <hjc@rock-chips.com>,
	Andy Yan <andy.yan@rock-chips.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	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>,
	Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Huseyin BIYIK <boogiepop@gmx.com>,
	Johan Jonker <jbx6244@yandex.com>
Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drm: devm_drm_bridge_alloc() conversion and cleanup
Date: Fri, 16 Oct 2026 13:45:22 +0200	[thread overview]
Message-ID: <2372538.iZASKD2KPV@diego> (raw)
In-Reply-To: <d1f0369c-ff43-4b76-9092-5c638b132f15@yandex.com>

Hi Johan,

Am Freitag, 16. Oktober 2026, 10:11:19 Mitteleuropäische Sommerzeit schrieb Johan Jonker:
> If any decency or Code of Conduct left in the DRM group then also credit the original author.
> Also remove driver_private.

after letting that stew in my mind over a lunch break:

- yes, your patch was earlier
- yes, I should've gotten around to it earlier - I am sorry about that
- so yes, this got mishandled

Nevertheless, this in no way justifies attacking the "drm-group", which
consists of a big number of individuals (most of which had no contact with
either variant of the patch at all) on a personal level :-( .

The change itself of moving to devm_drm_bridge_alloc, also is somewhat
straight-forward  that two different people could easily just create the
same change separately, as we saw here.


Heiko


> ===
> 
> [PATCH v3] drm/rockchip: rk3066_hdmi: convert to devm_drm_bridge_alloc() API
> https://lore.kernel.org/linux-rockchip/20260904-drm-v3-1-5b36532a3b72@gmail.com/  
> 
> [PATCH v2] drm/rockchip: rk3066_hdmi: convert to devm_drm_bridge_alloc() API
> https://lore.kernel.org/linux-rockchip/20260824-drm-v2-1-7f9273c6020b@gmail.com/
> 
> https://lore.kernel.org/linux-rockchip/dea8a038-577b-45da-bff3-703e9099b7e1@gmail.com/
> [PATCH v1] drm/rockchip: rk3066_hdmi: convert to devm_drm_bridge_alloc() API
> 
> On 10/16/26 08:52, Luca Ceresoli wrote:
> > 
> > On Thu, 01 Oct 2026 11:25:10 +0300, Cristian Ciocaltea wrote:
> >> Bridge drivers are expected to allocate their private data via
> >> devm_drm_bridge_alloc(), which also initializes the embedded struct
> >> drm_bridge, including its funcs pointer.  Most drivers were converted by
> >> commit 9c399719cfb9 ("drm: convert many bridge drivers from
> >> devm_kzalloc() to devm_drm_bridge_alloc() API"), but a couple of
> >> leftovers remain.
> >>
> >> [...]
> > 
> > Applied, thanks!
> > 
> > [1/2] drm/rockchip: rk3066_hdmi: Convert to devm_drm_bridge_alloc() API
> >       commit: 5c0cdbee4fa4a621f871d6dc825e759db08a1a4a
> > [2/2] drm/bridge: lontium-lt8713sx: Drop redundant bridge funcs assignment
> >       commit: 382c1e8ba409d1611cd256dccebdfa828c832bb1
> > 
> > Best regards,
> 
> 





_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

      parent reply	other threads:[~2026-10-16 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  8:25 [PATCH 0/2] drm: devm_drm_bridge_alloc() conversion and cleanup Cristian Ciocaltea
2026-10-01  8:25 ` [PATCH 1/2] drm/rockchip: rk3066_hdmi: Convert to devm_drm_bridge_alloc() API Cristian Ciocaltea
2026-10-01  8:28   ` Maxime Ripard
2026-10-01 16:31   ` Luca Ceresoli
2026-10-01  8:25 ` [PATCH 2/2] drm/bridge: lontium-lt8713sx: Drop redundant bridge funcs assignment Cristian Ciocaltea
2026-10-01  8:29   ` Maxime Ripard
2026-10-01 16:31   ` Luca Ceresoli
2026-10-16  6:52 ` [PATCH 0/2] drm: devm_drm_bridge_alloc() conversion and cleanup Luca Ceresoli
2026-10-16  8:11   ` Johan Jonker
2026-10-16  9:32     ` Cristian Ciocaltea
2026-10-16 10:01     ` Luca Ceresoli
2026-10-16 11:45     ` Heiko Stübner [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=2372538.iZASKD2KPV@diego \
    --to=heiko@sntech.de \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andy.yan@rock-chips.com \
    --cc=boogiepop@gmx.com \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hjc@rock-chips.com \
    --cc=jbx6244@yandex.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.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