Bug 92251

Summary: SSH account request for libdrm
Product: DRI Reporter: Michel Thierry <michel.thierry>
Component: libdrmAssignee: Default DRI bug account <dri-devel>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
SSH Key
none
GPG Key none

Description Michel Thierry 2015-10-02 15:34:10 UTC
Created attachment 118613 [details]
SSH Key

Hi,

I like to get an account to continue my work in i915 and libdrm, which requires merging a patch in the later, and releasing a new version of it.

Name: Michel Thierry
Email: michel.thierry@intel.com
Account: mthierry

SSH and GPG public keys are attached.

Thanks
Comment 1 Michel Thierry 2015-10-02 15:34:46 UTC
Created attachment 118614 [details]
GPG Key
Comment 2 Emil Velikov 2015-10-02 15:51:44 UTC
Has the kernel patches landed upstream ? If so I can merge the patch(es) and roll out a release. Considering that everything is reviewed, of course ;-)
Comment 3 Michel Thierry 2015-10-02 15:53:57 UTC
Yes it has,
http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-next-queued&id=101b506a7fc7be3f0d0a337ade270eb5eb5a2857

Let me check if the libdrm patch needs a rebase.

Thanks
Comment 4 Michel Thierry 2015-10-02 17:09:44 UTC
The patch still applies cleanly and passed make distcheck...

http://lists.freedesktop.org/archives/dri-devel/2015-September/089757.html (ack'd by MichaƂ), plus the symbol-check test update http://lists.freedesktop.org/archives/dri-devel/2015-September/089758.html

But let me know if it's better to resend them anyway.

Thanks
Comment 5 Emil Velikov 2016-12-12 13:34:38 UTC
Michel, I believe that the respective patches has found their way upstream and we have a few releases which include them.
Comment 6 Michel Thierry 2016-12-12 15:42:25 UTC
Correct, and this is no longer needed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.