From: "Christian König" <christian.koenig@amd.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
Gustavo Padovan <gustavo@padovan.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dma-buf: fix kernel-doc warning in <linux/dma-buf.h>
Date: Mon, 31 Aug 2020 12:00:04 +0200 [thread overview]
Message-ID: <b97f98ed-75b7-400c-07d3-89f49c5bb809@amd.com> (raw)
In-Reply-To: <20200831041655.29796-1-rdunlap@infradead.org>
Am 31.08.20 um 06:16 schrieb Randy Dunlap:
> Fix kernel-doc warning in <linux/dma-buf.h>:
>
> ../include/linux/dma-buf.h:330: warning: Function parameter or member 'name_lock' not described in 'dma_buf'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> Cc: Gustavo Padovan <gustavo@padovan.org>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: linux-media@vger.kernel.org
> Cc: dri-devel@lists.freedesktop.org
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> include/linux/dma-buf.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> --- lnx-59-rc3.orig/include/linux/dma-buf.h
> +++ lnx-59-rc3/include/linux/dma-buf.h
> @@ -283,6 +283,7 @@ struct dma_buf_ops {
> * @exp_name: name of the exporter; useful for debugging.
> * @name: userspace-provided name; useful for accounting and debugging,
> * protected by @resv.
> + * @name_lock: spinlock to protect name access
> * @owner: pointer to exporter module; used for refcounting when exporter is a
> * kernel module.
> * @list_node: node for dma_buf accounting and debugging.
> @@ -311,7 +312,7 @@ struct dma_buf {
> void *vmap_ptr;
> const char *exp_name;
> const char *name;
> - spinlock_t name_lock; /* spinlock to protect name access */
> + spinlock_t name_lock;
> struct module *owner;
> struct list_head list_node;
> void *priv;
prev parent reply other threads:[~2020-08-31 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 4:16 Randy Dunlap
2020-08-31 10:00 ` Christian König [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=b97f98ed-75b7-400c-07d3-89f49c5bb809@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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
all inboxes | Powered by JetHome®