linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>,
	 Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH -next] mm/munlock: Fix kernel-doc formatting issues
Date: Wed, 9 Feb 2022 18:20:46 -0800 (PST)	[thread overview]
Message-ID: <9eceb01a-4a62-985f-52c-266cabc156f9@google.com> (raw)
In-Reply-To: <20220210004849.69017-1-yang.lee@linux.alibaba.com>

On Thu, 10 Feb 2022, Yang Li wrote:

> Some functions had kernel-doc that used a hash instead of a colon to
> separate the parameter name from the one line description.
> 
> Replacing them to remove warnings found by running scripts/kernel-doc,
> which is caused by using 'make W=1'.
> 
> mm/mlock.c:218: warning: Function parameter or member 'page' not
> described in 'mlock_page'
> mm/mlock.c:240: warning: Function parameter or member 'page' not
> described in 'mlock_new_page'
> mm/mlock.c:260: warning: Function parameter or member 'page' not
> described in 'munlock_page'
> 
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>

Oh, great, thanks.  I thought I was just following what was already
there, but now I look closer, yes, the ones with "/*" at the top had
dashes and the ones with "/**" at the top had colons: apparently I fell
for the wrong combination - sorry.

Hugh

> ---
>  mm/mlock.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/mlock.c b/mm/mlock.c
> index d50d48961b22..7fb97e1242f1 100644
> --- a/mm/mlock.c
> +++ b/mm/mlock.c
> @@ -212,7 +212,7 @@ bool need_mlock_page_drain(int cpu)
>  
>  /**
>   * mlock_page - mlock a page already on (or temporarily off) LRU
> - * @page - page to be mlocked, either a normal page or a THP head.
> + * @page: page to be mlocked, either a normal page or a THP head.
>   */
>  void mlock_page(struct page *page)
>  {
> @@ -234,7 +234,7 @@ void mlock_page(struct page *page)
>  
>  /**
>   * mlock_new_page - mlock a newly allocated page not yet on LRU
> - * @page - page to be mlocked, either a normal page or a THP head.
> + * @page: page to be mlocked, either a normal page or a THP head.
>   */
>  void mlock_new_page(struct page *page)
>  {
> @@ -254,7 +254,7 @@ void mlock_new_page(struct page *page)
>  
>  /**
>   * munlock_page - munlock a page
> - * @page - page to be munlocked, either a normal page or a THP head.
> + * @page: page to be munlocked, either a normal page or a THP head.
>   */
>  void munlock_page(struct page *page)
>  {
> -- 
> 2.20.1.7.g153144c


      reply	other threads:[~2022-02-10  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  0:48 [PATCH -next] mm/munlock: Fix kernel-doc formatting issues Yang Li
2022-02-10  2:20 ` Hugh Dickins [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=9eceb01a-4a62-985f-52c-266cabc156f9@google.com \
    --to=hughd@google.com \
    --cc=abaci@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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).