All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
	Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
	Nick Terrell <terrelln@fb.com>, Schspa Shi <schspa@gmail.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: zstd: remove extraneous asterix at the head of zstd_reclaim_timer_fn() comment
Date: Mon, 18 Apr 2022 11:29:11 -0400	[thread overview]
Message-ID: <Yl2Dx+jefYs1Un+8@localhost.localdomain> (raw)
In-Reply-To: <20220418125934.566647-1-bagasdotme@gmail.com>

On Mon, Apr 18, 2022 at 07:59:35PM +0700, Bagas Sanjaya wrote:
> kernel test robot reports kernel-doc warning:
> 
> >> fs/btrfs/zstd.c:98: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> 
> The comment is for zstd_reclaim_timer_fn(). Since the function is
> static, the comment isn't meant for kernel-doc consumption.
> 
> Remove the extraneous (second) asterix at the head of function comment.
> 
> Link: https://lore.kernel.org/linux-doc/202204151934.CkKcnvuJ-lkp@intel.com/
> Fixes: b672526e2ee935 ("btrfs: use non-bh spin_lock in zstd timer callback")
> Cc: Chris Mason <clm@fb.com>
> Cc: Josef Bacik <josef@toxicpanda.com>
> Cc: David Sterba <dsterba@suse.com>
> Cc: Nick Terrell <terrelln@fb.com>
> Cc: Schspa Shi <schspa@gmail.com>
> Cc: linux-btrfs@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

  reply	other threads:[~2022-04-18 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 12:59 [PATCH] btrfs: zstd: remove extraneous asterix at the head of zstd_reclaim_timer_fn() comment Bagas Sanjaya
2022-04-18 15:29 ` Josef Bacik [this message]
2022-04-19  5:19   ` Bagas Sanjaya
2022-04-19 13:06     ` David Sterba

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=Yl2Dx+jefYs1Un+8@localhost.localdomain \
    --to=josef@toxicpanda.com \
    --cc=bagasdotme@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schspa@gmail.com \
    --cc=terrelln@fb.com \
    --cc=willy@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.