From: Hans de Goede <hdegoede@redhat.com>
To: Wang Hai <wanghai38@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fs: vboxsf: Fix a kernel-doc warning in vboxsf_wrappers.c
Date: Fri, 11 Sep 2020 14:05:59 +0200 [thread overview]
Message-ID: <03f07277-d80a-f652-1050-472124db5900@redhat.com> (raw)
In-Reply-To: <20200911114339.62308-1-wanghai38@huawei.com>
Hi,
On 9/11/20 1:43 PM, Wang Hai wrote:
> Fixes the following W=1 kernel build warning(s):
>
> fs/vboxsf/vboxsf_wrappers.c:132: warning: Excess function parameter 'param' description in 'vboxsf_create'
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
Thank you, looks good to me:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> fs/vboxsf/vboxsf_wrappers.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/vboxsf/vboxsf_wrappers.c b/fs/vboxsf/vboxsf_wrappers.c
> index bfc78a097dae..3b6630e2847d 100644
> --- 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: 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
>
prev parent reply other threads:[~2020-09-11 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 11:43 [PATCH -next] fs: vboxsf: Fix a kernel-doc warning in vboxsf_wrappers.c Wang Hai
2020-09-11 12:05 ` Hans de Goede [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=03f07277-d80a-f652-1050-472124db5900@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wanghai38@huawei.com \
/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).