From: Steven Liu <lingjiujianke@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, adilger@sun.com, linux-kernel@vger.kernel.org
Subject: [PATCH] ext4: Fix coding style in fs/ext4/move_extent.c
Date: Wed, 17 Mar 2010 18:12:14 +0800 [thread overview]
Message-ID: <bd0d95d71003170312s10fd8680xcbea67cc8d681296@mail.gmail.com> (raw)
fix a code style in fs/ext4/move_extent.c
Signed-off-by: LiuQi <lingjiujianke@gmail.com>
---
fs/ext4/move_extent.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/ext4/move_extent.c b/fs/ext4/move_extent.c
index aa5fe28..b399358 100644
--- a/fs/ext4/move_extent.c
+++ b/fs/ext4/move_extent.c
@@ -481,6 +481,7 @@ mext_leaf_block(handle_t *handle, struct inode *orig_inode,
int depth = ext_depth(orig_inode);
int ret;
+ start_ext.ee_block = end_ext.ee_block = 0;
o_start = o_end = oext = orig_path[depth].p_ext;
oext_alen = ext4_ext_get_actual_len(oext);
start_ext.ee_len = end_ext.ee_len = 0;
--
1.6.0.3
next reply other threads:[~2010-03-17 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 10:12 Steven Liu [this message]
2010-03-22 0:20 ` [PATCH] ext4: Fix coding style in fs/ext4/move_extent.c tytso
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=bd0d95d71003170312s10fd8680xcbea67cc8d681296@mail.gmail.com \
--to=lingjiujianke@gmail.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).