Re: [PATCH 2/3] drm/etnaviv: Expose our reservation object when exporting a dmabuf.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lucas Stach <l.stach@xxxxxxxxxxxxxx> writes:

> Am Mittwoch, den 12.04.2017, 14:47 +0200 schrieb Daniel Vetter:
>> On Mon, Apr 10, 2017 at 06:44:13PM -0700, Eric Anholt wrote:
>> > Without this, polling on the dma-buf (and presumably other devices
>> > synchronizing against our rendering) would return immediately, even
>> > while the BO was busy.
>> > 
>> > Signed-off-by: Eric Anholt <eric@xxxxxxxxxx>
>> > Cc: stable@xxxxxxxxxxxxxxx
>> > Cc: Lucas Stach <l.stach@xxxxxxxxxxxxxx>
>> > Cc: Russell King <linux+etnaviv@xxxxxxxxxxxxxxx>
>> > Cc: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
>> > Cc: etnaviv@xxxxxxxxxxxxxxxxxxxxx
>> 
>> On the first 2 patches:
>> 
>> Reviewed-by: Daniel Vetter <daniel.vetter@xxxxxxxx>
>> 
>> If you get an ack from Rob/Lucas I guess we could push these also through
>> drm-misc.
>
> Patch itself looks fine. I prefer to route the etnaviv change through my
> tree, to give it the usual exposure to our testing.

Yeah, I'd rather you grab it so you can test it before it lands.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]