public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.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>,
	John Harrison <John.C.Harrison@Intel.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>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH v3 1/4] dma-buf/fence-array: add fence_is_array()
Date: Tue, 5 Jul 2016 14:26:37 +0200	[thread overview]
Message-ID: <577BA77D.2020504@amd.com> (raw)
In-Reply-To: <1467676628-4121-2-git-send-email-gustavo@padovan.org>

Am 05.07.2016 um 01:57 schrieb Gustavo Padovan:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Add helper to check if fence is array.
>
> v2: Comments from Chris Wilson
> 	- remove ternary if from ops comparison
> 	- add EXPORT_SYMBOL(fence_array_ops)
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Christian König <christian.koenig@amd.com>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

For this patch Reviewed-by: Christian König <christian.koenig@amd.com>.

I'm not deep enough into the sync file code to fully judge, but the 
remaining patches look good to me as well.

So for patch #2-#4 Acked-by: Christian König <christian.koenig@amd.com>.

Regards,
Christian.

> ---
>   drivers/dma-buf/fence-array.c |  1 +
>   include/linux/fence-array.h   | 10 ++++++++++
>   2 files changed, 11 insertions(+)
>
> diff --git a/drivers/dma-buf/fence-array.c b/drivers/dma-buf/fence-array.c
> index a8731c8..ee50022 100644
> --- a/drivers/dma-buf/fence-array.c
> +++ b/drivers/dma-buf/fence-array.c
> @@ -99,6 +99,7 @@ const struct fence_ops fence_array_ops = {
>   	.wait = fence_default_wait,
>   	.release = fence_array_release,
>   };
> +EXPORT_SYMBOL(fence_array_ops);
>   
>   /**
>    * fence_array_create - Create a custom fence array
> diff --git a/include/linux/fence-array.h b/include/linux/fence-array.h
> index 86baaa4..a44794e 100644
> --- a/include/linux/fence-array.h
> +++ b/include/linux/fence-array.h
> @@ -52,6 +52,16 @@ struct fence_array {
>   extern const struct fence_ops fence_array_ops;
>   
>   /**
> + * fence_is_array - check if a fence is from the array subsclass
> + *
> + * Return true if it is a fence_array and false otherwise.
> + */
> +static inline bool fence_is_array(struct fence *fence)
> +{
> +	return fence->ops == &fence_array_ops;
> +}
> +
> +/**
>    * to_fence_array - cast a fence to a fence_array
>    * @fence: fence to cast to a fence_array
>    *

  reply	other threads:[~2016-07-05 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 23:57 [PATCH v3 0/4] dma-buf/sync_file: rework fences on struct sync_file Gustavo Padovan
2016-07-04 23:57 ` [PATCH v3 1/4] dma-buf/fence-array: add fence_is_array() Gustavo Padovan
2016-07-05 12:26   ` Christian König [this message]
2016-07-04 23:57 ` [PATCH v3 2/4] dma-buf/sync_file: rework fence storage in struct file Gustavo Padovan
2016-07-04 23:57 ` [PATCH v3 3/4] dma-buf/sync_file: add sync_file_get_fence() Gustavo Padovan
2016-07-04 23:57 ` [PATCH v3 4/4] Documentation: add doc for sync_file_get_fence() 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=577BA77D.2020504@amd.com \
    --to=christian.koenig@amd.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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