[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160812084441.GR6232@phenom.ffwll.local>
Date: Fri, 12 Aug 2016 10:44:41 +0200
From: Daniel Vetter <daniel@...ll.ch>
To: Sumit Semwal <sumit.semwal@...aro.org>
Cc: linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, corbet@....net
Subject: Re: [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section
header
On Thu, Aug 11, 2016 at 04:17:58PM +0530, Sumit Semwal wrote:
> Commit e941759c74a44d6ac2eed21bb0a38b21fe4559e2 ("fence: dma-buf
> cross-device synchronization (v18)") had a spurious kerneldoc section
> header that caused Sphinx to complain. Fix it.
>
> Fixes: e941759c74a4 ("fence: dma-buf cross-device synchronization (v18)")
>
> Signed-off-by: Sumit Semwal <sumit.semwal@...aro.org>
On patches 1&2 Reviewed-by: Daniel Vetter <daniel.vetter@...ll.ch>
> ---
> include/linux/fence.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/fence.h b/include/linux/fence.h
> index 5aa95eb886f7..5de89dab0013 100644
> --- a/include/linux/fence.h
> +++ b/include/linux/fence.h
> @@ -60,7 +60,7 @@ struct fence_cb;
> * implementer of the fence for its own purposes. Can be used in different
> * ways by different fence implementers, so do not rely on this.
> *
> - * *) Since atomic bitops are used, this is not guaranteed to be the case.
> + * Since atomic bitops are used, this is not guaranteed to be the case.
> * Particularly, if the bit was set, but fence_signal was called right
> * before this bit was set, it would have been able to set the
> * FENCE_FLAG_SIGNALED_BIT, before enable_signaling was called.
> --
> 2.7.4
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@...ts.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists