From: Michael Banack <banackm@vmware.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Albert Esteve <aesteve@redhat.com>,
qemu-devel@nongnu.org
Cc: linux-doc@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
Gerd Hoffmann <kraxel@redhat.com>,
mombasawalam@vmware.com, iforbes@vmware.com,
Jonathan Corbet <corbet@lwn.net>,
VMware Graphics Reviewers <linux-graphics-maintainer@vmware.com>,
David Airlie <airlied@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
ppaalanen@gmail.com, spice-devel@lists.freedesktop.org,
Gurchetan Singh <gurchetansingh@chromium.org>,
Matt Roper <matthew.d.roper@intel.com>,
linux-kernel@vger.kernel.org, krastevm@vmware.com
Subject: Re: [PATCH v6 9/9] drm: Introduce documentation for hotspot properties
Date: Tue, 24 Oct 2023 12:34:23 -0700 [thread overview]
Message-ID: <1bbee4ad-79fe-4968-0edc-3eee34ad5972@vmware.com> (raw)
In-Reply-To: <87h6mh10zg.fsf@minerva.mail-host-address-is-not-set>
Yes, that patch should be:
Signed-off-by: Michael Banack <banackm@vmware.com>
--Michael Banack
On 10/23/23 14:29, Javier Martinez Canillas wrote:
> Albert Esteve <aesteve@redhat.com> writes:
>
>> From: Michael Banack <banackm@vmware.com>
>>
>> To clarify the intent and reasoning behind the hotspot properties
>> introduce userspace documentation that goes over cursor handling
>> in para-virtualized environments.
>>
>> The documentation is generic enough to not special case for any
>> specific hypervisor and should apply equally to all.
>>
>> Signed-off-by: Zack Rusin <zackr@vmware.com>
> The author is Michael Banack but it's missing a SoB from them.
> I don't think there's a need to resend for this, can be added
> when applying. But either Michael or Zack should confirm that
> is the correct thing to do for this patch.
>
> The doc itself looks great to me and it clarifies a lot about
> cursor hotspots.
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
>
next prev parent reply other threads:[~2023-10-24 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 7:46 [PATCH v6 0/9] Fix cursor planes with virtualized drivers Albert Esteve
2023-10-23 7:46 ` [PATCH v6 1/9] drm: Disable the cursor plane on atomic contexts " Albert Esteve
2023-10-23 7:53 ` Simon Ser
2023-10-23 7:46 ` [PATCH v6 2/9] drm/atomic: Add support for mouse hotspots Albert Esteve
2023-10-23 7:46 ` [PATCH v6 3/9] drm/vmwgfx: Use the hotspot properties from cursor planes Albert Esteve
2023-10-23 7:46 ` [PATCH v6 4/9] drm/qxl: " Albert Esteve
2023-10-23 7:46 ` [PATCH v6 5/9] drm/vboxvideo: " Albert Esteve
2023-10-23 7:46 ` [PATCH v6 6/9] drm/virtio: " Albert Esteve
2023-10-23 7:46 ` [PATCH v6 7/9] drm: Remove legacy cursor hotspot code Albert Esteve
2023-10-23 7:46 ` [PATCH v6 8/9] drm: Introduce DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT Albert Esteve
2023-10-23 7:46 ` [PATCH v6 9/9] drm: Introduce documentation for hotspot properties Albert Esteve
2023-10-23 8:23 ` Pekka Paalanen
2023-10-23 21:29 ` Javier Martinez Canillas
2023-10-24 19:34 ` Michael Banack [this message]
2023-10-25 6:36 ` Javier Martinez Canillas
2023-10-23 7:55 ` [PATCH v6 0/9] Fix cursor planes with virtualized drivers Simon Ser
2023-10-23 8:14 ` Albert Esteve
2023-10-23 8:19 ` Simon Ser
2023-11-22 12:49 ` Javier Martinez Canillas
2023-11-23 22:11 ` Simon Ser
2023-11-24 10:56 ` Javier Martinez Canillas
2023-11-24 14:41 ` 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=1bbee4ad-79fe-4968-0edc-3eee34ad5972@vmware.com \
--to=banackm@vmware.com \
--cc=aesteve@redhat.com \
--cc=airlied@redhat.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=hdegoede@redhat.com \
--cc=iforbes@vmware.com \
--cc=javierm@redhat.com \
--cc=krastevm@vmware.com \
--cc=kraxel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.d.roper@intel.com \
--cc=mombasawalam@vmware.com \
--cc=mripard@kernel.org \
--cc=ppaalanen@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
/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).