From: Tomohiro Kusumi <tkusumi@tuxera.com>
To: <viro@zeniv.linux.org.uk>, <linux-fsdevel@vger.kernel.org>,
<trond.myklebust@primarydata.com>, <anna.schumaker@netapp.com>,
<linux-nfs@vger.kernel.org>
Cc: Tomohiro Kusumi <tkusumi@tuxera.com>
Subject: [PATCH 3/3] fs/mpage: fix a comment "get_blocks" to "get_block"
Date: Tue, 28 Feb 2017 21:45:23 +0200 [thread overview]
Message-ID: <20170228194523.2054-3-tkusumi@tuxera.com> (raw)
In-Reply-To: <20170228194523.2054-1-tkusumi@tuxera.com>
It's a get_block_t argument get_block being called here.
Signed-off-by: Tomohiro Kusumi <tkusumi@tuxera.com>
---
fs/mpage.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/mpage.c b/fs/mpage.c
index 28af984..67e9492 100644
--- a/fs/mpage.c
+++ b/fs/mpage.c
@@ -173,7 +173,7 @@ do_mpage_readpage(struct bio *bio, struct page *page, unsigned nr_pages,
page_block = 0;
/*
- * Map blocks using the result from the previous get_blocks call first.
+ * Map blocks using the result from the previous get_block call first.
*/
nblocks = map_bh->b_size >> blkbits;
if (buffer_mapped(map_bh) && block_in_file > *first_logical_block &&
@@ -197,7 +197,7 @@ do_mpage_readpage(struct bio *bio, struct page *page, unsigned nr_pages,
}
/*
- * Then do more get_blocks calls until we are done with this page.
+ * Then do more get_block calls until we are done with this page.
*/
map_bh->b_page = page;
while (page_block < blocks_per_page) {
--
2.9.3
prev parent reply other threads:[~2017-02-28 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 19:45 [PATCH 1/3] fs/libfs: use SEEK_CUR/SET Tomohiro Kusumi
2017-02-28 19:45 ` [PATCH 2/3] nfs: " Tomohiro Kusumi
2017-02-28 19:45 ` Tomohiro Kusumi [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=20170228194523.2054-3-tkusumi@tuxera.com \
--to=tkusumi@tuxera.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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).