All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Alain Volmat" <alain.volmat@foss.st.com>,
	"David Airlie" <airlied@gmail.com>,
	"Hui Pu" <Hui.Pu@gehealthcare.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Raphael Gallais-Pou" <rgallaispou@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH 1/2] drm/sti: hdmi: convert to devm_drm_bridge_alloc() API
Date: Wed, 09 Jul 2025 07:30:37 +0000	[thread overview]
Message-ID: <c3fe3daf0a1e91d6ed8153a3a043eb5f@kernel.org> (raw)
In-Reply-To: <20250708-drm-bridge-convert-to-alloc-api-leftovers-v1-1-6285de8c3759@bootlin.com>

On Tue, 8 Jul 2025 17:24:42 +0200, Luca Ceresoli wrote:
> devm_drm_bridge_alloc() is the new API to be used for allocating (and
> partially initializing) a private driver struct embedding a struct
> drm_bridge.
> 
> This driver was missed during the automated conversion in commit
> 
> [ ... ]

Reviewed-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

  reply	other threads:[~2025-07-09  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 15:24 [PATCH 0/2] drm: fix missing conversions of bridge drivers to devm_drm_bridge_alloc() Luca Ceresoli
2025-07-08 15:24 ` [PATCH 1/2] drm/sti: hdmi: convert to devm_drm_bridge_alloc() API Luca Ceresoli
2025-07-09  7:30   ` Maxime Ripard [this message]
2025-07-08 15:24 ` [PATCH 2/2] drm/sti: hda: " Luca Ceresoli
2025-07-09  7:32   ` Maxime Ripard
2025-07-09  9:22     ` Luca Ceresoli
2025-07-09  9:35 ` [PATCH 0/2] drm: fix missing conversions of bridge drivers to devm_drm_bridge_alloc() Luca Ceresoli
2025-07-09 12:05   ` Maxime Ripard
2025-07-09 15:17     ` 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=c3fe3daf0a1e91d6ed8153a3a043eb5f@kernel.org \
    --to=mripard@kernel.org \
    --cc=Hui.Pu@gehealthcare.com \
    --cc=airlied@gmail.com \
    --cc=alain.volmat@foss.st.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=m.szyprowski@samsung.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=rgallaispou@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.petazzoni@bootlin.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.