From: Zack Rusin <zackr@vmware.com>
To: "javierm@redhat.com" <javierm@redhat.com>,
"contact@emersion.fr" <contact@emersion.fr>
Cc: "aesteve@redhat.com" <aesteve@redhat.com>,
Michael Banack <banackm@vmware.com>,
Martin Krastev <krastevm@vmware.com>,
"ppaalanen@gmail.com" <ppaalanen@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Ian Forbes <iforbes@vmware.com>,
Maaz Mombasawala <mombasawalam@vmware.com>
Subject: Re: [PATCH v5 9/9] drm: Introduce documentation for hotspot properties
Date: Thu, 20 Jul 2023 19:28:31 +0000 [thread overview]
Message-ID: <b4f00adeeaec35aacd008fe7a6ca9283760f6421.camel@vmware.com> (raw)
In-Reply-To: <YpGDUfd-_k9UGRn9xM-lwrWFXim3YiYG1wzgbk_lvSTQ2JL3zxxDuZef4ZTJe_NtOlwMMDy5OoDqK-Ia4VN3p-fibO_gaR7t6pH3oxyEI8Y=@emersion.fr>
On Thu, 2023-07-20 at 09:07 +0000, Simon Ser wrote:
> !! External Email
>
> On Thursday, July 20th, 2023 at 10:50, Javier Martinez Canillas
> <javierm@redhat.com> wrote:
>
> > > On Thursday, July 20th, 2023 at 07:03, Zack Rusin zackr@vmware.com wrote:
> > >
> > > > I'll give this series a few more hours on the list and if no one objects
> > > > I'll push
> > > > it to drm-misc later today. Thanks!
> > >
> > > Sorry, but this doesn't seem to be enough to satisfy the DRM merge
> > > requirements. This introduces a new uAPI but is missing user-space
> > > patches and IGT. See 1 and 2.
> >
> >
> > Albert (Cc'ed) wrote IGT tests for this new uAPI and was waiting for
> > Zack's patches to land to post them. I believe his branch is [0] but
> > he can correct me if I'm wrong on that.
> >
> > Zack also has mutter patches and Albert has been testing those too.
> >
> > [0]:
> > https://gitlab.freedesktop.org/aesteve/igt-gpu-tools/-/commits/modeset-cursor-hotspot-test/
>
> Ah, nice. Please do post all of these (without merging them) and
> include links to them in the commit message. Posting is important
> to make sure there are no gaps/mistakes in the tests and user-space
> impl.
What should those links point to? Because my private mutter repository is definitely
not going to last long so I'm not sure if there's any point in putting that in a
kernel commit log. Or would you like the links to those in the cover letter?
z
next prev parent reply other threads:[~2023-07-20 19:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 1:42 [PATCH v5 0/9] Fix cursor planes with virtualized drivers Zack Rusin
2023-07-19 1:42 ` [PATCH v5 1/9] drm: Disable the cursor plane on atomic contexts " Zack Rusin
2023-07-20 9:46 ` Simon Ser
2023-07-19 1:42 ` [PATCH v5 2/9] drm/atomic: Add support for mouse hotspots Zack Rusin
2023-07-20 9:20 ` Simon Ser
2023-07-19 1:42 ` [PATCH v5 3/9] drm/vmwgfx: Use the hotspot properties from cursor planes Zack Rusin
2023-07-19 1:42 ` [PATCH v5 4/9] drm/qxl: " Zack Rusin
2023-07-19 1:42 ` [PATCH v5 5/9] drm/vboxvideo: " Zack Rusin
2023-07-19 1:42 ` [PATCH v5 6/9] drm/virtio: " Zack Rusin
2023-07-19 1:42 ` [PATCH v5 7/9] drm: Remove legacy cursor hotspot code Zack Rusin
2023-07-19 1:42 ` [PATCH v5 8/9] drm: Introduce DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT Zack Rusin
2023-07-20 9:54 ` Simon Ser
2023-07-19 1:42 ` [PATCH v5 9/9] drm: Introduce documentation for hotspot properties Zack Rusin
2023-07-19 7:53 ` Javier Martinez Canillas
2023-07-19 8:15 ` Pekka Paalanen
2023-07-20 5:03 ` Zack Rusin
2023-07-20 6:47 ` Simon Ser
2023-07-20 8:50 ` Javier Martinez Canillas
2023-07-20 9:07 ` Simon Ser
2023-07-20 19:28 ` Zack Rusin [this message]
2023-07-20 19:32 ` Simon Ser
2023-07-24 11:04 ` Albert Esteve
2023-08-10 11:06 ` Albert Esteve
2023-07-20 9:51 ` Simon Ser
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=b4f00adeeaec35aacd008fe7a6ca9283760f6421.camel@vmware.com \
--to=zackr@vmware.com \
--cc=aesteve@redhat.com \
--cc=banackm@vmware.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=iforbes@vmware.com \
--cc=javierm@redhat.com \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.com \
--cc=ppaalanen@gmail.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