[prev in list] [next in list] [prev in thread] [next in thread]
List: dri-devel
Subject: Re: [PATCH v5 9/9] drm: Introduce documentation for hotspot properties
From: Albert Esteve <aesteve () redhat ! com>
Date: 2023-07-24 11:04:38
Message-ID: CADSE00Ld7D8E8MG6cc7HAgM_DbqXqYreik4ZZLUhkkJDW3B=Yg () mail ! gmail ! com
[Download RAW message or body]
On Thu, Jul 20, 2023 at 9:32 PM Simon Ser <contact@emersion.fr> wrote:
> On Thursday, July 20th, 2023 at 21:28, Zack Rusin <zackr@vmware.com>
> wrote:
>
> > 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.
> > >
> > > 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?
>
> The kernel docs say: "The userspace side must be fully reviewed and
> tested to the standards of that userspace project".
>
> So you need to open a merge request for mutter. Same for IGT.
>
>
Hi,
Here's the link to the IGT patch:
https://lists.freedesktop.org/archives/igt-dev/2023-July/058427.html
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr"><div><div dir="ltr" class="gmail_signature"><div \
dir="ltr"><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Jul 20, 2023 at 9:32 PM Simon Ser <<a \
href="mailto:contact@emersion.fr">contact@emersion.fr</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thursday, July \
20th, 2023 at 21:28, Zack Rusin <<a href="mailto:zackr@vmware.com" \
target="_blank">zackr@vmware.com</a>> wrote:<br> <br>
> On Thu, 2023-07-20 at 09:07 +0000, Simon Ser wrote:<br>
> <br>
> > !! External Email<br>
> > <br>
> > On Thursday, July 20th, 2023 at 10:50, Javier Martinez Canillas<br>
> > <a href="mailto:javierm@redhat.com" target="_blank">javierm@redhat.com</a> \
wrote:<br> > > <br>
> > > > On Thursday, July 20th, 2023 at 07:03, Zack Rusin <a \
href="mailto:zackr@vmware.com" target="_blank">zackr@vmware.com</a> wrote:<br> > \
> > > <br> > > > > > I'll give this series a few more \
hours on the list and if no one objects<br> > > > > > I'll \
push<br> > > > > > it to drm-misc later today. Thanks!<br>
> > > > <br>
> > > > Sorry, but this doesn't seem to be enough to satisfy the DRM \
merge<br> > > > > requirements. This introduces a new uAPI but is missing \
user-space<br> > > > > patches and IGT. See 1 and 2.<br>
> > > <br>
> > > Albert (Cc'ed) wrote IGT tests for this new uAPI and was waiting \
for<br> > > > Zack's patches to land to post them. I believe his branch \
is 0 but<br> > > > he can correct me if I'm wrong on that.<br>
> > > <br>
> > > Zack also has mutter patches and Albert has been testing those \
too.<br> > > <br>
> > Ah, nice. Please do post all of these (without merging them) and<br>
> > include links to them in the commit message. Posting is important<br>
> > to make sure there are no gaps/mistakes in the tests and user-space<br>
> > impl.<br>
> <br>
> What should those links point to? Because my private mutter repository is \
definitely<br> > not going to last long so I'm not sure if there's any \
point in putting that in a<br> > kernel commit log. Or would you like the links to \
those in the cover letter?<br> <br>
The kernel docs say: "The userspace side must be fully reviewed and<br>
tested to the standards of that userspace project".<br>
<br>
So you need to open a merge request for mutter. Same for IGT.<br>
<br></blockquote><div><br></div><div>Hi,</div><div><br></div><div>Here's the link \
to the IGT patch: <a \
href="https://lists.freedesktop.org/archives/igt-dev/2023-July/058427.html">https://lists.freedesktop.org/archives/igt-dev/2023-July/058427.html</a></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic