From: "Maxime Ripard" <mripard@kernel.org>
To: "Louis Chauvet" <louis.chauvet@bootlin.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, "David Airlie" <airlied@gmail.com>,
"Haneen Mohammed" <hamohammed.sa@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Maíra Canal" <mairacanal@riseup.net>,
"Melissa Wen" <melissa.srw@gmail.com>,
"Rodrigo Siqueira" <rodrigosiqueiramelo@gmail.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"Simona Vetter" <simona@ffwll.ch>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v2 1/4] drm/vkms: Switch to dynamic allocation for connector
Date: Wed, 27 Nov 2024 15:14:55 +0000 [thread overview]
Message-ID: <0fdc00c3d39563fa06cf8ac022e36d43@kernel.org> (raw)
In-Reply-To: <20241122-b4-vkms-allocated-v2-1-ff7bddbf0bfb@bootlin.com>
On Fri, 22 Nov 2024 17:35:09 +0100, Louis Chauvet wrote:
> A specific allocation for the connector is not strictly necessary
> at this point, but in order to implement dynamic configuration of
> VKMS (configFS), it will be easier to have one allocation per
> connector.
>
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2024-11-27 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 16:35 [PATCH v2 0/4] drm/vkms: Switch to allocated for drm objects Louis Chauvet
2024-11-22 16:35 ` [PATCH v2 1/4] drm/vkms: Switch to dynamic allocation for connector Louis Chauvet
2024-11-27 15:14 ` Maxime Ripard [this message]
2024-11-22 16:35 ` [PATCH v2 2/4] drm/vkms: Switch to dynamic allocation for encoder Louis Chauvet
2024-11-27 15:15 ` Maxime Ripard
2024-11-22 16:35 ` [PATCH v2 3/4] drm/vkms: Switch to dynamic allocation for CRTC Louis Chauvet
2024-11-27 15:19 ` Maxime Ripard
2024-12-03 15:23 ` José Expósito
2024-11-22 16:35 ` [PATCH v2 4/4] drm/vkms: Rename vkms_output to vkms_crtc Louis Chauvet
2024-11-27 15:21 ` Maxime Ripard
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=0fdc00c3d39563fa06cf8ac022e36d43@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=simona.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox