From: Matthew Wilcox <willy@infradead.org>
To: rohitsd1409 <rohitsd1409@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] inode_dio_begin comment fixed.
Date: Wed, 17 Nov 2021 13:13:06 +0000 [thread overview]
Message-ID: <YZT/4nVVjylycZBs@casper.infradead.org> (raw)
In-Reply-To: <20211117111326.GA4306@overlay>
On Wed, Nov 17, 2021 at 04:43:26PM +0530, rohitsd1409 wrote:
> +++ b/include/linux/fs.h
> @@ -3282,8 +3282,7 @@ void inode_dio_wait(struct inode *inode);
> * inode_dio_begin - signal start of a direct I/O requests
> * @inode: inode the direct I/O happens on
> *
> - * This is called once we've finished processing a direct I/O request,
> - * and is used to wake up callers waiting for direct I/O to be quiesced.
> + * This is called once we've started processing a direct I/O request.
> */
* This is called before we start processing a direct I/O request so
* that inode_dio_wait() will wait for this to finish.
prev parent reply other threads:[~2021-11-17 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:13 [PATCH] inode_dio_begin comment fixed rohitsd1409
2021-11-17 13:13 ` Matthew Wilcox [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=YZT/4nVVjylycZBs@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rohitsd1409@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).