From: Geliang Tang <geliangtang@gmail.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Geliang Tang <geliangtang@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fs/buffer: use i_blocksize()
Date: Fri, 20 Jan 2017 22:29:50 +0800 [thread overview]
Message-ID: <c049bd6bfe984b617e0503cfc6c56ec4bb2aea7b.1484895183.git.geliangtang@gmail.com> (raw)
In-Reply-To: <0a58b38c7ddfbbc8f56cb8d815114bd4357a6016.1484895399.git.geliangtang@gmail.com>
Since i_blocksize() helper has been defined in fs.h, use it instead
of open-coding.
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
---
fs/buffer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/buffer.c b/fs/buffer.c
index 28484b3..53612c4 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -243,7 +243,7 @@ __find_get_block_slow(struct block_device *bdev, sector_t block)
printk("b_state=0x%08lx, b_size=%zu\n",
bh->b_state, bh->b_size);
printk("device %pg blocksize: %d\n", bdev,
- 1 << bd_inode->i_blkbits);
+ i_blocksize(bd_inode));
}
out_unlock:
spin_unlock(&bd_mapping->private_lock);
--
2.9.3
next prev parent reply other threads:[~2017-01-20 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 14:29 [PATCH] ext4: " Geliang Tang
2017-01-20 14:29 ` Geliang Tang [this message]
2017-01-20 14:29 ` [PATCH] isofs: " Geliang Tang
2017-01-20 14:29 ` [PATCH] md/bitmap: " Geliang Tang
2017-01-20 15:00 ` Coly Li
2017-01-21 18:13 ` Shaohua Li
2017-01-22 1:50 ` Geliang Tang
2017-05-02 14:33 ` Geliang Tang
2017-01-20 14:29 ` [PATCH] staging: lustre: " Geliang Tang
2017-01-20 23:34 ` James Simmons
2017-01-20 14:29 ` [PATCH] truncate: " Geliang Tang
2017-01-20 17:39 ` Ross Zwisler
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=c049bd6bfe984b617e0503cfc6c56ec4bb2aea7b.1484895183.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®