On Thursday, July 20th, 2023 at 21:28, Zack Rusin <za...@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 > > javi...@redhat.com wrote: > > > > > > On Thursday, July 20th, 2023 at 07:03, Zack Rusin za...@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.
