From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Hans de Goede <hdegoede@redhat.com>,
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, 06 Dec 2023 10:16:58 -0700 [thread overview]
Message-ID: <87lea7b69h.fsf@meer.lwn.net> (raw)
In-Reply-To: <bec63fe6-b9d7-4aff-bee6-d5c137554d71@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> On 12/6/23 06:57, Hans de Goede wrote:
>> 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
>
> I have no idea, but we can ask Jon.
>
> Jon, can you merge this patch thru the Documentation tree?
I've not actually seen the patch but, yes, I should be able to do that.
Will go dig it out in a bit.
Thanks,
jon
prev parent reply other threads:[~2023-12-06 17:16 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
2023-12-06 16:49 ` Randy Dunlap
2023-12-06 17:16 ` Jonathan Corbet [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=87lea7b69h.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=brauner@kernel.org \
--cc=hdegoede@redhat.com \
--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).