From: Sheng Yong <shengyong1@huawei.com>
To: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH trivial 3/7] fsck.f2fs: correct variable type and name
Date: Fri, 15 Jul 2016 20:01:21 +0800 [thread overview]
Message-ID: <1468584085-29090-3-git-send-email-shengyong1@huawei.com> (raw)
In-Reply-To: <1468584085-29090-1-git-send-email-shengyong1@huawei.com>
Signed-off-by: Sheng Yong <shengyong1@huawei.com>
---
fsck/fsck.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index 8a6373b..f349bd8 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -736,7 +736,7 @@ void fsck_chk_inode_blk(struct f2fs_sb_info *sbi, u32 nid,
/* check node blocks in inode */
for (idx = 0; idx < 5; idx++) {
- block_t blkaddr = le32_to_cpu(node_blk->i.i_nid[idx]);
+ nid_t i_nid = le32_to_cpu(node_blk->i.i_nid[idx]);
if (idx == 0 || idx == 1)
ntype = TYPE_DIRECT_NODE;
@@ -747,11 +747,10 @@ void fsck_chk_inode_blk(struct f2fs_sb_info *sbi, u32 nid,
else
ASSERT(0);
- if (blkaddr == 0x0)
+ if (i_nid == 0x0)
goto skip;
- ret = fsck_chk_node_blk(sbi, &node_blk->i,
- blkaddr,
+ ret = fsck_chk_node_blk(sbi, &node_blk->i, i_nid,
NULL, ftype, ntype, blk_cnt, &child);
if (!ret) {
*blk_cnt = *blk_cnt + 1;
--
2.7.1
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
next prev parent reply other threads:[~2016-07-15 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 12:01 [PATCH trivial 1/7] dump.f2fs: show inode->i_dir_level Sheng Yong
2016-07-15 12:01 ` [PATCH trivial 2/7] f2fs.fsck: fix endianess Sheng Yong
2016-07-15 12:01 ` Sheng Yong [this message]
2016-07-15 12:01 ` [PATCH trivial 4/7] fsck.f2fs: fix typo Sheng Yong
2016-07-15 12:01 ` [PATCH trivial 5/7] fsck.f2fs: free nat entry cache Sheng Yong
2016-07-15 12:01 ` [PATCH trivial 6/7] f2fs-tools: update the format of output message Sheng Yong
2016-07-15 12:01 ` [PATCH trivial 7/7] fsck.f2fs: clean up duplicated code Sheng Yong
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=1468584085-29090-3-git-send-email-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).