From: zwu.kernel@gmail.com
To: xfs@oss.sgi.com
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH 09/12] xfs: fix the comment of xfs_log_unmount_write()
Date: Mon, 12 Aug 2013 11:15:00 +0800 [thread overview]
Message-ID: <1376277303-29455-10-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_log.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
index 0fd27dc..6fd274c 100644
--- a/fs/xfs/xfs_log.c
+++ b/fs/xfs/xfs_log.c
@@ -720,7 +720,7 @@ xfs_log_mount_finish(xfs_mount_t *mp)
* Unmount record used to have a string "Unmount filesystem--" in the
* data section where the "Un" was really a magic number (XLOG_UNMOUNT_TYPE).
* We just write the magic number now since that particular field isn't
- * currently architecture converted and "nUmount" is a bit foo.
+ * currently architecture converted and "Unmount" is a bit foo.
* As far as I know, there weren't any dependencies on the old behaviour.
*/
--
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 ` [PATCH 04/12] xfs: fix the comment of xfs_bmap_punch_delalloc_range() zwu.kernel
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 ` zwu.kernel [this message]
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-10-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox