From: Sumit Semwal <sumit.semwal@linaro.org> To: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, linux-doc@vger.kernel.org Cc: corbet@lwn.net, linux-kernel@vger.kernel.org, Sumit Semwal <sumit.semwal@linaro.org> Subject: [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Date: Thu, 11 Aug 2016 16:17:58 +0530 [thread overview] Message-ID: <1470912480-32304-3-git-send-email-sumit.semwal@linaro.org> (raw) In-Reply-To: <1470912480-32304-1-git-send-email-sumit.semwal@linaro.org> 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@linaro.org> --- 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
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Semwal <sumit.semwal@linaro.org> To: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, corbet@lwn.net Subject: [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Date: Thu, 11 Aug 2016 16:17:58 +0530 [thread overview] Message-ID: <1470912480-32304-3-git-send-email-sumit.semwal@linaro.org> (raw) In-Reply-To: <1470912480-32304-1-git-send-email-sumit.semwal@linaro.org> 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@linaro.org> --- 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@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-11 10:48 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-11 10:47 [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal 2016-08-11 10:47 ` [RFC 1/4] dma-buf/fence: kerneldoc: remove unused struct members Sumit Semwal 2016-08-11 10:47 ` Sumit Semwal 2016-08-11 10:47 ` Sumit Semwal [this message] 2016-08-11 10:47 ` [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Sumit Semwal 2016-08-12 8:44 ` Daniel Vetter 2016-08-12 8:44 ` Daniel Vetter 2016-08-11 10:47 ` [RFC 3/4] Documentation: move dma-buf documentation to rst Sumit Semwal 2016-08-11 10:47 ` Sumit Semwal 2016-08-11 11:47 ` Jani Nikula 2016-08-11 11:47 ` Jani Nikula 2016-08-11 12:31 ` Sumit Semwal 2016-08-11 11:58 ` Markus Heiser 2016-08-11 12:12 ` Markus Heiser 2016-08-11 12:12 ` Markus Heiser 2016-08-11 12:49 ` Sumit Semwal 2016-08-11 12:49 ` Sumit Semwal 2016-08-11 10:48 ` [RFC 4/4] Documentation/sphinx: link dma-buf rsts Sumit Semwal 2016-08-11 10:48 ` Sumit Semwal 2016-08-11 14:36 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Jonathan Corbet 2016-08-11 19:13 ` rst htmldocs on kernel.org Lukas Wunner 2016-08-15 22:21 ` Jonathan Corbet 2016-08-16 8:24 ` Lukas Wunner 2016-08-12 6:35 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal 2016-08-12 6:35 ` Sumit Semwal 2016-08-12 8:38 ` Daniel Vetter 2016-08-12 8:38 ` Daniel Vetter
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=1470912480-32304-3-git-send-email-sumit.semwal@linaro.org \ --to=sumit.semwal@linaro.org \ --cc=corbet@lwn.net \ --cc=dri-devel@lists.freedesktop.org \ --cc=linaro-mm-sig@lists.linaro.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.