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 v3 3/3] drm/vkms: Switch to dynamic allocation for CRTC
Date: Mon, 06 Jan 2025 09:10:13 +0000 [thread overview]
Message-ID: <f0e86f5019904c0d5295306d1a075fd4@kernel.org> (raw)
In-Reply-To: <20241230-b4-vkms-allocated-v3-3-5dda4c1bd459@bootlin.com>
On Mon, 30 Dec 2024 19:39:46 +0100, Louis Chauvet wrote:
> A specific allocation for the CRTC 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 CRTC.
>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
prev parent reply other threads:[~2025-01-06 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 18:39 [PATCH v3 0/3] drm/vkms: Switch to allocated for drm objects Louis Chauvet
2024-12-30 18:39 ` [PATCH v3 1/3] drm/vkms: Switch to dynamic allocation for connector Louis Chauvet
2024-12-30 18:39 ` [PATCH v3 2/3] drm/vkms: Switch to dynamic allocation for encoder Louis Chauvet
2024-12-30 18:39 ` [PATCH v3 3/3] drm/vkms: Switch to dynamic allocation for CRTC Louis Chauvet
2025-01-06 9:10 ` 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=f0e86f5019904c0d5295306d1a075fd4@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 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.