From: Eric Anholt <eric@anholt.net>
To: Lucas Stach <l.stach@pengutronix.de>, Daniel Vetter <daniel@ffwll.ch>
Cc: stable@vger.kernel.org,
Russell King <linux+etnaviv@armlinux.org.uk>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
etnaviv@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/etnaviv: Expose our reservation object when exporting a dmabuf.
Date: Wed, 12 Apr 2017 10:32:38 -0700 [thread overview]
Message-ID: <87zifl7cqx.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1492001645.15082.14.camel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
Lucas Stach <l.stach@pengutronix.de> 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@anholt.net>
>> > Cc: stable@vger.kernel.org
>> > Cc: Lucas Stach <l.stach@pengutronix.de>
>> > Cc: Russell King <linux+etnaviv@armlinux.org.uk>
>> > Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
>> > Cc: etnaviv@lists.freedesktop.org
>>
>> On the first 2 patches:
>>
>> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-04-12 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 1:44 [PATCH 1/3] drm/msm: " Eric Anholt
2017-04-11 1:44 ` [PATCH 2/3] drm/etnaviv: " Eric Anholt
2017-04-12 12:47 ` Daniel Vetter
2017-04-12 12:54 ` Lucas Stach
2017-04-12 17:32 ` Eric Anholt [this message]
2017-04-11 1:44 ` [PATCH 3/3] drm/vc4: Add support for dma-buf fencing Eric Anholt
2017-04-11 9:35 ` Chris Wilson
2017-04-11 17:43 ` Eric Anholt
2017-04-12 12:49 ` Daniel Vetter
2017-04-12 12:48 ` Daniel Vetter
2017-04-12 17:33 ` Eric Anholt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zifl7cqx.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®