linux-kernel - Re: [PATCH libdrm 0/6] drm-next header syncing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 10 Nov 2017 11:30:34 +0000
From:   Emil Velikov <emil.l.velikov@...il.com>
To:     Eric Anholt <eric@...olt.net>,
        ML dri-devel <dri-devel@...ts.freedesktop.org>,
        "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH libdrm 0/6] drm-next header syncing

On 9 November 2017 at 08:28, Daniel Vetter <daniel@...ll.ch> wrote:
> On Wed, Nov 08, 2017 at 11:34:41AM -0800, Eric Anholt wrote:
>> I wanted to update the vc4 header so that I could land some igt
>> testcases (though I'd much rather just be importing the header into
>> igt and ditching libdrm).  In the process, I cleaned up some other
>> header deltas to the kernel so that there's less diff for the next
>> person to look at.
>
> I'm mildly tempted to just pull a mesa in igt too and put the headers in
> directly. To avoid the need for way too many libdrm releases when hacking
> on tests we atm add all the uapi stuff with a local_ prefix, but that's
> kinda silly.
>
> Maybe start a thread with vc4 as example converted (I guess we need to
> make sure the include order is right) to get this started.

That shouldn't be an obstacle to merging Eric's patches, right?

I went through the series and it looks good. For the lot
Reviewed-by: Emil Velikov <emil.l.velikov@...il.com>

-Emil