From: Robert Foss <robert.foss@collabora.com>
To: Gustavo Padovan <gustavo@padovan.org>, dri-devel@lists.freedesktop.org
Cc: marcheu@google.com, Daniel Stone <daniels@collabora.com>,
seanpaul@google.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
John Harrison <John.C.Harrison@Intel.com>,
m.chehab@samsung.com
Subject: Re: [PATCH v8 0/3] drm: add explict fencing
Date: Fri, 11 Nov 2016 09:50:26 -0500 [thread overview]
Message-ID: <1478875826.2080.1.camel@collabora.com> (raw)
In-Reply-To: <1478873759-6580-1-git-send-email-gustavo@padovan.org>
I tested this series on the db410c platform and I've seen no
regressions from previous versions of this series.
Tested-by: Robert Foss <robert.foss@collabora.com>
next prev parent reply other threads:[~2016-11-11 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 14:15 [PATCH v8 0/3] drm: add explict fencing Gustavo Padovan
2016-11-11 14:15 ` [PATCH v8 1/3] drm/fence: add in-fences support Gustavo Padovan
2016-11-11 15:42 ` Sean Paul
2016-11-11 14:15 ` [PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc Gustavo Padovan
2016-11-11 14:15 ` [PATCH v8 3/3] drm/fence: add out-fences support Gustavo Padovan
2016-11-11 16:48 ` Sean Paul
2016-11-11 17:11 ` Daniel Vetter
2016-11-11 17:21 ` Sean Paul
2016-11-11 17:38 ` Brian Starkey
2016-11-11 14:17 ` [PATCH v8 0/3] drm: add explict fencing Gustavo Padovan
2016-11-11 14:50 ` Robert Foss [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-11 5:16 Gustavo Padovan
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=1478875826.2080.1.camel@collabora.com \
--to=robert.foss@collabora.com \
--cc=John.C.Harrison@Intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=marcheu@google.com \
--cc=seanpaul@google.com \
/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