linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Su Yue <suy.fnst@cn.fujitsu.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: correct wrong comment about magic number of index_cnt
Date: Fri, 12 Jan 2018 11:18:31 +0800	[thread overview]
Message-ID: <69eb939f-d1f2-ec00-1b8c-1ea0c4f65631@cn.fujitsu.com> (raw)
In-Reply-To: <20180112030803.28341-1-suy.fnst@cn.fujitsu.com>

Sorry, the two patches are same.
Please the latter one.

Thanks,
Su

On 01/12/2018 11:08 AM, Su Yue wrote:
> There is no function named btrfs_get_inode_index_count.
> Explanation for magic number index_cnt=2 in btrfs_new_inode() is
> actually located in btrfs_set_inode_index_count().
> 
> So replace 'btrfs_get_inode_index_count' in the comment by
> 'btrfs_set_inode_index_count'.
> 
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
> ---
>   fs/btrfs/inode.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 37bdb78b4766..f6454719192e 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -6315,7 +6315,7 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans,
>   	}
>   	/*
>   	 * index_cnt is ignored for everything but a dir,
> -	 * btrfs_get_inode_index_count has an explanation for the magic
> +	 * btrfs_set_inode_index_count has an explanation for the magic
>   	 * number
>   	 */
>   	BTRFS_I(inode)->index_cnt = 2;
> 



      parent reply	other threads:[~2018-01-12  3:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12  3:08 [PATCH] btrfs: correct wrong comment about magic number of index_cnt Su Yue
2018-01-12  3:08 ` Su Yue
2018-01-16 15:22   ` David Sterba
2018-01-12  3:18 ` Su Yue [this message]

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=69eb939f-d1f2-ec00-1b8c-1ea0c4f65631@cn.fujitsu.com \
    --to=suy.fnst@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).