From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luis de Bethencourt <luisbg@osg.samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] include/linux: fix excess fence.h kernel-doc notation
Date: Mon, 15 Aug 2016 20:13:05 -0300 [thread overview]
Message-ID: <20160815231305.GE12212@joana> (raw)
In-Reply-To: <979639c6-369b-c9ad-10d6-7982b048f1fb@infradead.org>
2016-08-15 Randy Dunlap <rdunlap@infradead.org>:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix excess fields in kernel-doc notation in <linux/fence.h>
> after some struct fields were removed.
>
> Fixes these kernel-doc warnings:
> ..//include/linux/fence.h:85: warning: Excess struct/union/enum/typedef member 'child_list' description in 'fence'
> ..//include/linux/fence.h:85: warning: Excess struct/union/enum/typedef member 'active_list' description in 'fence'
>
> Fixes: 0431b9065f28 ("staging/android: bring struct sync_pt back")
>
> Cc: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Luis de Bethencourt <luisbg@osg.samsung.com>
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> include/linux/fence.h | 2 --
> 1 file changed, 2 deletions(-)
>
> --- lnx-48-rc2.orig/include/linux/fence.h
> +++ lnx-48-rc2/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
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Gustavo
prev parent reply other threads:[~2016-08-15 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 22:52 Randy Dunlap
2016-08-15 23:13 ` Gustavo Padovan [this message]
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=20160815231305.GE12212@joana \
--to=gustavo.padovan@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=rdunlap@infradead.org \
--cc=sumit.semwal@linaro.org \
--cc=torvalds@linux-foundation.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®