public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Bo Liu <liubo03@inspur.com>
Cc: <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fat (exportfs): Fix some kernel-doc warnings
Date: Fri, 11 Nov 2022 20:08:05 +0900	[thread overview]
Message-ID: <87wn8121gq.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20221111075648.4005-1-liubo03@inspur.com> (Bo Liu's message of "Fri, 11 Nov 2022 02:56:48 -0500")

Bo Liu <liubo03@inspur.com> writes:

> Fixes the following W=1 kernel build warning(s):
>   fs/fat/nfs.c:21: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>   fs/fat/nfs.c:139: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>
> Signed-off-by: Bo Liu <liubo03@inspur.com>

Looks good.

Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

> ---
>  fs/fat/nfs.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fat/nfs.c b/fs/fat/nfs.c
> index af191371c352..3626eb585a98 100644
> --- a/fs/fat/nfs.c
> +++ b/fs/fat/nfs.c
> @@ -17,7 +17,7 @@ struct fat_fid {
>  #define FAT_FID_SIZE_WITHOUT_PARENT 3
>  #define FAT_FID_SIZE_WITH_PARENT (sizeof(struct fat_fid)/sizeof(u32))
>  
> -/**
> +/*
>   * Look up a directory inode given its starting cluster.
>   */
>  static struct inode *fat_dget(struct super_block *sb, int i_logstart)
> @@ -135,7 +135,7 @@ fat_encode_fh_nostale(struct inode *inode, __u32 *fh, int *lenp,
>  	return type;
>  }
>  
> -/**
> +/*
>   * Map a NFS file handle to a corresponding dentry.
>   * The dentry may or may not be connected to the filesystem root.
>   */

-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      reply	other threads:[~2022-11-11 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  7:56 [PATCH] fat (exportfs): Fix some kernel-doc warnings Bo Liu
2022-11-11 11:08 ` OGAWA Hirofumi [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=87wn8121gq.fsf@mail.parknet.co.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo03@inspur.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