From: Baoquan He <bhe@redhat.com>
To: Yang Li <yang.lee@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] proc/vmcore: Fix vmcore_alloc_buf() kernel-doc comment
Date: Sat, 29 Jan 2022 15:53:57 +0800 [thread overview]
Message-ID: <20220129075357.GB17613@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220129011449.105278-1-yang.lee@linux.alibaba.com>
On 01/29/22 at 09:14am, Yang Li wrote:
> Fix a spelling problem to remove warnings found
> by running scripts/kernel-doc, which is caused by
> using 'make W=1'.
>
> fs/proc/vmcore.c:492: warning: Function parameter or member 'size' not
> described in 'vmcore_alloc_buf'
> fs/proc/vmcore.c:492: warning: Excess function parameter 'sizez'
> description in 'vmcore_alloc_buf'
Acked-by: Baoquan He <bhe@redhat.com>
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> fs/proc/vmcore.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c
> index edeb01dfe05d..6f1b8ddc6f7a 100644
> --- a/fs/proc/vmcore.c
> +++ b/fs/proc/vmcore.c
> @@ -480,7 +480,7 @@ static const struct vm_operations_struct vmcore_mmap_ops = {
>
> /**
> * vmcore_alloc_buf - allocate buffer in vmalloc memory
> - * @sizez: size of buffer
> + * @size: size of buffer
> *
> * If CONFIG_MMU is defined, use vmalloc_user() to allow users to mmap
> * the buffer to user-space by means of remap_vmalloc_range().
> --
> 2.20.1.7.g153144c
>
prev parent reply other threads:[~2022-01-29 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 1:14 [PATCH -next] proc/vmcore: Fix vmcore_alloc_buf() kernel-doc comment Yang Li
2022-01-29 7:53 ` Baoquan He [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=20220129075357.GB17613@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=abaci@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=yang.lee@linux.alibaba.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).