From: zwu.kernel@gmail.com
To: xfs@oss.sgi.com
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH 04/12] xfs: fix the comment of xfs_bmap_punch_delalloc_range()
Date: Mon, 12 Aug 2013 11:14:55 +0800 [thread overview]
Message-ID: <1376277303-29455-5-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1376277303-29455-1-git-send-email-zwu.kernel@gmail.com>
From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
fs/xfs/xfs_bmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_bmap.c b/fs/xfs/xfs_bmap.c
index 0a838a3..1d077c2 100644
--- a/fs/xfs/xfs_bmap.c
+++ b/fs/xfs/xfs_bmap.c
@@ -6074,7 +6074,7 @@ xfs_getbmap(
/*
* dead simple method of punching delalyed allocation blocks from a range in
* the inode. Walks a block at a time so will be slow, but is only executed in
- * rare error cases so the overhead is not critical. This will alays punch out
+ * rare error cases so the overhead is not critical. This will always punch out
* both the start and end blocks, even if the ranges only partially overlap
* them, so it is up to the caller to ensure that partial blocks are not
* passed in.
--
1.7.11.7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-12 3:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 3:14 [PATCH 00/12] xfs: another chunk of comment fixes zwu.kernel
2013-08-12 3:14 ` [PATCH 01/12] xfs: fix the comment of xfs_bmap_count_tree() zwu.kernel
2013-08-12 3:14 ` [PATCH 02/12] xfs: fix the comment of xfs_bmap_validate_ret() zwu.kernel
2013-08-12 3:14 ` [PATCH 03/12] xfs: fix the comment of xfs_bmap_last_before() zwu.kernel
2013-08-12 3:14 ` zwu.kernel [this message]
2013-08-12 3:14 ` [PATCH 05/12] xfs: fix the comment of xfs_setsize_buftarg_early() zwu.kernel
2013-08-12 3:14 ` [PATCH 06/12] xfs: fix the comment of xfs_extent_busy_update_extent() zwu.kernel
2013-08-19 18:27 ` Mark Tinguely
2013-08-19 19:36 ` Zhi Yong Wu
2013-08-12 3:14 ` [PATCH 07/12] xfs: fix the comment of xfs_ialloc_ag_select() zwu.kernel
2013-08-12 3:14 ` [PATCH 08/12] xfs: fix the comment of xfs_ifree_cluster() zwu.kernel
2013-08-12 3:15 ` [PATCH 09/12] xfs: fix the comment of xfs_log_unmount_write() zwu.kernel
2013-08-12 3:15 ` [PATCH 10/12] xfs: fix the comment of xlog_recover_do_dquot_buffer() zwu.kernel
2013-08-12 3:15 ` [PATCH 11/12] xfs: fix the comment of xfs_sb_quiet_read_verify() zwu.kernel
2013-08-12 3:15 ` [PATCH 12/12] xfs: fix the comment of xfs_mountfs() zwu.kernel
2013-08-19 18:39 ` [PATCH 00/12] xfs: another chunk of comment fixes Mark Tinguely
2013-08-20 21:17 ` Ben Myers
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=1376277303-29455-5-git-send-email-zwu.kernel@gmail.com \
--to=zwu.kernel@gmail.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.