From: Mark Tinguely <tinguely@sgi.com>
To: zwu.kernel@gmail.com
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 06/12] xfs: fix the comment of xfs_extent_busy_update_extent()
Date: Mon, 19 Aug 2013 13:27:29 -0500 [thread overview]
Message-ID: <52126391.8050800@sgi.com> (raw)
In-Reply-To: <1376277303-29455-7-git-send-email-zwu.kernel@gmail.com>
On 08/11/13 22:14, zwu.kernel@gmail.com wrote:
> From: Zhi Yong Wu<wuzhy@linux.vnet.ibm.com>
>
> Signed-off-by: Zhi Yong Wu<wuzhy@linux.vnet.ibm.com>
> ---
> fs/xfs/xfs_extent_busy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_extent_busy.c b/fs/xfs/xfs_extent_busy.c
> index 85e9f87..4ad8fee 100644
> --- a/fs/xfs/xfs_extent_busy.c
> +++ b/fs/xfs/xfs_extent_busy.c
> @@ -147,7 +147,7 @@ xfs_extent_busy_search(
> * extent. If the overlap covers the beginning, the end, or all of the busy
> * extent, the overlapping portion can be made unbusy and used for the
> * allocation. We can't split a busy extent because we can't modify a
> - * transaction/CIL context busy list, but we can update an entries block
> + * transaction/CIL context busy list, but we can update an entrie's block
^^^^^^
changed that to entry's
> * number or length.
> *
> * Returns true if the extent can safely be reused, or false if the search
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-19 18:27 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 [this message]
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=52126391.8050800@sgi.com \
--to=tinguely@sgi.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
--cc=zwu.kernel@gmail.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.