From: rohitsd1409 <rohitsd1409@gmail.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH] inode_dio_begin comment fixed.
Date: Wed, 17 Nov 2021 16:43:26 +0530 [thread overview]
Message-ID: <20211117111326.GA4306@overlay> (raw)
inode_dio_begin and inode_dio_end have same comment "This is called once
we have finished processing ...". This comment is applicable only for
inode_dio_end and someone copy pasted it for inode_dio_begin also.
Hence, updated the comment for inode_dio_begin by adding correct
explanation.
---
include/linux/fs.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 1cb616fc1105..2fb075da88a4 100644
--- a/include/linux/fs.h
+++ 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.
*/
static inline void inode_dio_begin(struct inode *inode)
{
--
2.17.1
next reply other threads:[~2021-11-17 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:13 rohitsd1409 [this message]
2021-11-17 13:13 ` [PATCH] inode_dio_begin comment fixed Matthew Wilcox
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=20211117111326.GA4306@overlay \
--to=rohitsd1409@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--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).