linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-fsdevel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] fs: vboxsf: fix a kernel-doc warning
Date: Wed, 6 Dec 2023 15:57:03 +0100	[thread overview]
Message-ID: <0fb8fe4f-cb5d-4c74-9bdc-34ff04024f62@redhat.com> (raw)
In-Reply-To: <20231206025355.31814-1-rdunlap@infradead.org>

Hi Randy,

On 12/6/23 03:53, Randy Dunlap wrote:
> Fix function parameters to prevent kernel-doc warnings.
> 
> vboxsf_wrappers.c:132: warning: Function parameter or member 'create_parms' not described in 'vboxsf_create'
> vboxsf_wrappers.c:132: warning: Excess function parameter 'param' description in 'vboxsf_create'
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

vboxsf is not really undergoing any active development,
can this be merged through the Documentation tree?

Regards,

Hans





> ---
>  fs/vboxsf/vboxsf_wrappers.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -- a/fs/vboxsf/vboxsf_wrappers.c b/fs/vboxsf/vboxsf_wrappers.c
> --- a/fs/vboxsf/vboxsf_wrappers.c
> +++ b/fs/vboxsf/vboxsf_wrappers.c
> @@ -114,7 +114,7 @@ int vboxsf_unmap_folder(u32 root)
>   * vboxsf_create - Create a new file or folder
>   * @root:         Root of the shared folder in which to create the file
>   * @parsed_path:  The path of the file or folder relative to the shared folder
> - * @param:        create_parms Parameters for file/folder creation.
> + * @create_parms: Parameters for file/folder creation.
>   *
>   * Create a new file or folder or open an existing one in a shared folder.
>   * Note this function always returns 0 / success unless an exceptional condition
> 


  reply	other threads:[~2023-12-06 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  2:53 [PATCH] fs: vboxsf: fix a kernel-doc warning Randy Dunlap
2023-12-06 14:57 ` Hans de Goede [this message]
2023-12-06 16:49   ` Randy Dunlap
2023-12-06 17:16     ` Jonathan Corbet

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=0fb8fe4f-cb5d-4c74-9bdc-34ff04024f62@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).