From: Maxime Ripard <mripard@kernel.org>
To: Louis Chauvet <louis.chauvet@bootlin.com>
Cc: "Rodrigo Siqueira" <rodrigosiqueiramelo@gmail.com>,
"Maíra Canal" <mairacanal@riseup.net>,
"Haneen Mohammed" <hamohammed.sa@gmail.com>,
"Melissa Wen" <melissa.srw@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
thomas.petazzoni@bootlin.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] drm/vkms: Rename vkms_output to vkms_crtc
Date: Wed, 27 Nov 2024 16:21:00 +0100 [thread overview]
Message-ID: <20241127-aboriginal-spiked-centipede-cabef0@houat> (raw)
In-Reply-To: <20241122-b4-vkms-allocated-v2-4-ff7bddbf0bfb@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Fri, Nov 22, 2024 at 05:35:12PM +0100, Louis Chauvet wrote:
> The current vkms_output structure only contains crtc-related members.
That's not true though? There's a connector, the connector's workqueue,
etc. in there.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
prev parent reply other threads:[~2024-11-27 15:21 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
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 [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=20241127-aboriginal-spiked-centipede-cabef0@houat \
--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
all inboxes | Powered by JetHome®