From: John Harrison <John.C.Harrison@Intel.com>
To: Gustavo Padovan <gustavo@padovan.org>, dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
Daniel Stone <daniels@collabora.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Rob Clark <robdclark@gmail.com>,
Greg Hackmann <ghackmann@google.com>,
laurent.pinchart@ideasonboard.com, seanpaul@google.com,
marcheu@google.com, m.chehab@samsung.com,
Sumit Semwal <sumit.semwal@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v4 5/5] dma-buf/sync_file: only enable fence signalling on poll()
Date: Thu, 14 Jul 2016 14:21:00 +0100 [thread overview]
Message-ID: <9b3e5a0f-9cf3-9f75-b968-dc1510a97d95@Intel.com> (raw)
In-Reply-To: <1468346925-12774-5-git-send-email-gustavo@padovan.org>
On 12/07/2016 19:08, Gustavo Padovan wrote:
> ...
>
> +++ b/include/linux/sync_file.h
> @@ -28,6 +28,7 @@
> * @name: name of sync_file. Useful for debugging
> * @sync_file_list: membership in global file list
> * @wq: wait queue for fence signaling
> + * @enabled: wether fence signal is enabled or not
Minor typo: should be 'whether'.
next prev parent reply other threads:[~2016-07-14 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 18:08 [PATCH v4 1/5] dma-buf/fence-array: add fence_is_array() Gustavo Padovan
2016-07-12 18:08 ` [PATCH v4 2/5] dma-buf/sync_file: refactor fence storage in struct sync_file Gustavo Padovan
2016-07-19 12:15 ` Sumit Semwal
2016-07-19 12:21 ` Sumit Semwal
2016-07-28 11:00 ` Sumit Semwal
2016-07-28 14:26 ` Greg Kroah-Hartman
2016-07-12 18:08 ` [PATCH v4 3/5] dma-buf/sync_file: add sync_file_get_fence() Gustavo Padovan
2016-07-12 18:08 ` [PATCH v4 4/5] Documentation: add doc for sync_file_get_fence() Gustavo Padovan
2016-07-12 18:08 ` [PATCH v4 5/5] dma-buf/sync_file: only enable fence signalling on poll() Gustavo Padovan
2016-07-14 13:21 ` John Harrison [this message]
2016-08-03 11:43 ` Chris Wilson
2016-08-04 21:18 ` Gustavo Padovan
2016-08-04 21:32 ` Chris Wilson
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=9b3e5a0f-9cf3-9f75-b968-dc1510a97d95@Intel.com \
--to=john.c.harrison@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghackmann@google.com \
--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=maarten.lankhorst@linux.intel.com \
--cc=marcheu@google.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@google.com \
--cc=sumit.semwal@linaro.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®