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 1/4] dma-buf/fence: kerneldoc: remove unused struct members
Date: Thu, 11 Aug 2016 16:17:57 +0530 [thread overview]
Message-ID: <1470912480-32304-2-git-send-email-sumit.semwal@linaro.org> (raw)
In-Reply-To: <1470912480-32304-1-git-send-email-sumit.semwal@linaro.org>
Commit 0431b9065f28ecf6c320fefebe0241620049984f ("staging/android: bring
struct sync_pt back") removed child_list and active_list from struct fence,
but left it in kernel doc. Delete them.
Fixes: 0431b9065f28 ("staging/android: bring struct sync_pt back")
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
---
include/linux/fence.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/fence.h b/include/linux/fence.h
index 1de1b3f6fb76..5aa95eb886f7 100644
--- a/include/linux/fence.h
+++ b/include/linux/fence.h
@@ -49,8 +49,6 @@ struct fence_cb;
* @timestamp: Timestamp when the fence was signaled.
* @status: Optional, only valid if < 0, must be set before calling
* fence_signal, indicates that the fence has completed with an error.
- * @child_list: list of children fences
- * @active_list: list of active fences
*
* the flags member must be manipulated and read using the appropriate
* atomic ops (bit_*), so taking the spinlock will not be needed most
--
2.7.4
next prev parent reply other threads:[~2016-08-11 10:48 UTC|newest]
Thread overview: 14+ 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 ` 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-11 10:47 ` [RFC 3/4] Documentation: move dma-buf documentation to rst Sumit Semwal
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:49 ` Sumit Semwal
2016-08-11 10:48 ` [RFC 4/4] Documentation/sphinx: link dma-buf rsts Sumit Semwal
2016-08-11 14:36 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Jonathan Corbet
2016-08-12 6:35 ` Sumit Semwal
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-2-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: 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