From: Javier Martinez Canillas <javierm@redhat.com>
To: Zack Rusin <zackr@vmware.com>, dri-devel@lists.freedesktop.org
Cc: banackm@vmware.com, virtualization@lists.linux-foundation.org,
krastevm@vmware.com, ppaalanen@gmail.com,
Gerd Hoffmann <kraxel@redhat.com>,
spice-devel@lists.freedesktop.org,
Dave Airlie <airlied@redhat.com>,
iforbes@vmware.com, mombasawalam@vmware.com
Subject: Re: [PATCH v3 4/8] drm/qxl: Use the hotspot properties from cursor planes
Date: Tue, 27 Jun 2023 11:50:42 +0200 [thread overview]
Message-ID: <87ttut2pzh.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <20230627035839.496399-5-zack@kde.org>
Zack Rusin <zack@kde.org> writes:
> From: Zack Rusin <zackr@vmware.com>
>
> Atomic modesetting got support for mouse hotspots via the hotspot
> properties. Port the legacy kms hotspot handling to the new properties
> on cursor planes.
>
> Signed-off-by: Zack Rusin <zackr@vmware.com>
> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: virtualization@lists.linux-foundation.org
> Cc: spice-devel@lists.freedesktop.org
> ---
> drivers/gpu/drm/qxl/qxl_display.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-06-27 9:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:58 [PATCH v3 0/8] Fix cursor planes with virtualized drivers Zack Rusin
2023-06-27 3:58 ` [PATCH v3 1/8] drm: Disable the cursor plane on atomic contexts " Zack Rusin
2023-06-27 8:18 ` Pekka Paalanen
2023-06-27 8:26 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 2/8] drm/atomic: Add support for mouse hotspots Zack Rusin
2023-06-27 8:26 ` Pekka Paalanen
2023-06-27 8:56 ` Javier Martinez Canillas
2023-06-27 10:30 ` Pekka Paalanen
2023-06-27 10:54 ` Javier Martinez Canillas
2023-06-27 8:49 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 3/8] drm/vmwgfx: Use the hotspot properties from cursor planes Zack Rusin
2023-06-27 9:49 ` Javier Martinez Canillas
2023-06-27 13:08 ` Martin Krastev (VMware)
2023-06-27 3:58 ` [PATCH v3 4/8] drm/qxl: " Zack Rusin
2023-06-27 9:50 ` Javier Martinez Canillas [this message]
2023-06-27 3:58 ` [PATCH v3 5/8] drm/vboxvideo: " Zack Rusin
2023-06-27 10:02 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 6/8] drm/virtio: " Zack Rusin
2023-06-27 10:03 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 7/8] drm: Remove legacy cursor hotspot code Zack Rusin
2023-06-27 10:16 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 8/8] drm: Introduce DRM_CLIENT_CAP_VIRTUALIZED_CURSOR_PLANE Zack Rusin
2023-06-27 8:38 ` Pekka Paalanen
2023-06-27 10:19 ` Javier Martinez Canillas
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=87ttut2pzh.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=airlied@redhat.com \
--cc=banackm@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iforbes@vmware.com \
--cc=krastevm@vmware.com \
--cc=kraxel@redhat.com \
--cc=mombasawalam@vmware.com \
--cc=ppaalanen@gmail.com \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zackr@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).