From: Jeff Layton <jlayton@kernel.org>
To: David Howells <dhowells@redhat.com>,
Christian Brauner <brauner@kernel.org>
Cc: netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] netfs: Fix kdoc of netfs_read_subreq_progress()
Date: Wed, 16 Oct 2024 10:55:03 -0400 [thread overview]
Message-ID: <2cd3f82e359e5b6a27c752c29ef8688f8da20f1a.camel@kernel.org> (raw)
In-Reply-To: <1292002.1729090128@warthog.procyon.org.uk>
On Wed, 2024-10-16 at 15:48 +0100, David Howells wrote:
> Fix missing param description in kdoc of netfs_read_subreq_progress().
>
> Fixes: ee4cdf7ba857 ("netfs: Speed up buffered reading")
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Jeff Layton <jlayton@kernel.org>
> cc: netfs@lists.linux.dev
> cc: linux-fsdevel@vger.kernel.org
> ---
> fs/netfs/read_collect.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/netfs/read_collect.c b/fs/netfs/read_collect.c
> index 266ec8d20d92..2ef54d83cf59 100644
> --- a/fs/netfs/read_collect.c
> +++ b/fs/netfs/read_collect.c
> @@ -508,6 +508,7 @@ void netfs_wake_read_collector(struct netfs_io_request *rreq)
>
> /**
> * netfs_read_subreq_progress - Note progress of a read operation.
> + * @subreq: The I/O request that has made progress.
> *
> * This tells the read side of netfs lib that a contributory I/O operation has
> * made some progress and that it may be possible to unlock some folios.
>
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-10-16 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 14:48 [PATCH] netfs: Fix kdoc of netfs_read_subreq_progress() David Howells
2024-10-16 14:55 ` Jeff Layton [this message]
2024-10-17 11:03 ` David Howells
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=2cd3f82e359e5b6a27c752c29ef8688f8da20f1a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
/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).