linux-kernel - Re: [PATCH] dma-buf: fix kernel-doc warning and typos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 17 Aug 2016 08:35:25 +0530
From:	Sumit Semwal <sumit.semwal@...aro.org>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	Linaro MM SIG Mailman List <linaro-mm-sig@...ts.linaro.org>
Subject: Re: [PATCH] dma-buf: fix kernel-doc warning and typos

Hi Randy,

On 17 August 2016 at 05:01, Randy Dunlap <rdunlap@...radead.org> wrote:
> From: Randy Dunlap <rdunlap@...radead.org>
>
> Fix dma-buf kernel-doc warning and 2 minor typos in
> fence_array_create().
>
Thanks for your patch, I will queue it up!
> Fixes this warning:
> ..//drivers/dma-buf/fence-array.c:124: warning: No description found for parameter 'signal_on_any'
>
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Cc:     Sumit Semwal <sumit.semwal@...aro.org>
> Cc:     linux-media@...r.kernel.org
> Cc:     dri-devel@...ts.freedesktop.org
> Cc:     linaro-mm-sig@...ts.linaro.org
> ---
>  drivers/dma-buf/fence-array.c |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- lnx-48-rc2.orig/drivers/dma-buf/fence-array.c
> +++ lnx-48-rc2/drivers/dma-buf/fence-array.c
> @@ -106,14 +106,14 @@ const struct fence_ops fence_array_ops =
>   * @fences:            [in]    array containing the fences
>   * @context:           [in]    fence context to use
>   * @seqno:             [in]    sequence number to use
> - * @signal_on_any      [in]    signal on any fence in the array
> + * @signal_on_any:     [in]    signal on any fence in the array
>   *
>   * Allocate a fence_array object and initialize the base fence with fence_init().
>   * In case of error it returns NULL.
>   *
> - * The caller should allocte the fences array with num_fences size
> + * The caller should allocate the fences array with num_fences size
>   * and fill it with the fences it wants to add to the object. Ownership of this
> - * array is take and fence_put() is used on each fence on release.
> + * array is taken and fence_put() is used on each fence on release.
>   *
>   * If @signal_on_any is true the fence array signals if any fence in the array
>   * signals, otherwise it signals when all fences in the array signal.

Best,
Sumit.