public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, Hongbo Li <lihongbo22@huawei.com>,
	"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH 1/1] fs/iomap: Describle @private in iomap_readahead()
Date: Thu, 29 Jan 2026 17:21:53 +0800	[thread overview]
Message-ID: <4dd236c2-2ada-4d2b-a565-5c94904dcc23@linux.alibaba.com> (raw)
In-Reply-To: <20260126120020.675179-2-lihongbo22@huawei.com>

Hi Christian,

On 2026/1/26 20:00, Hongbo Li wrote:
> The kernel test rebot reports the kernel-doc warning:
> 
> ```
> Warning: fs/iomap/buffered-io.c:624 function parameter 'private'
>   not described in 'iomap_readahead'
> ```
> 
> The former commit in "iomap: stash iomap read ctx in the private
> field of iomap_iter" has added a new parameter @private to
> iomap_readahead(), so let's describe the parameter.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202601261111.vIL9rhgD-lkp@intel.com/
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>

Could you apply this single patch kernel-doc fix directly?

Thanks,
Gao Xiang

  parent reply	other threads:[~2026-01-29  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 12:00 [PATCH 0/1] fs/iomap: Describle @private in iomap_readahead() Hongbo Li
2026-01-26 12:00 ` [PATCH 1/1] " Hongbo Li
2026-01-26 12:38   ` Gao Xiang
2026-01-26 13:01     ` Hongbo Li
2026-01-26 13:08       ` Gao Xiang
2026-01-26 13:21         ` Hongbo Li
2026-01-26 12:44   ` Christoph Hellwig
2026-01-29  9:21   ` Gao Xiang [this message]
2026-02-03 13:25     ` Hongbo Li

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=4dd236c2-2ada-4d2b-a565-5c94904dcc23@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox