linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Chengguang Xu <cgxu519@zoho.com.cn>, <jaegeuk@kernel.org>,
	<chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix a comment in f2fs_shrink_count()
Date: Sun, 29 Sep 2019 08:56:25 +0800	[thread overview]
Message-ID: <0d773ecd-076e-54da-e952-8e6ad7894bb6@huawei.com> (raw)
In-Reply-To: <20190928014006.8243-1-cgxu519@zoho.com.cn>

Hi Chengguang,

Thanks a lot for the patch, previously I've sent a patch to fix most
inconsistent comments including below one, could you check that?

https://lore.kernel.org/linux-f2fs-devel/20190927102305.11587-1-yuchao0@huawei.com/T/#u

Thanks,

On 2019/9/28 9:40, Chengguang Xu via Linux-f2fs-devel wrote:
> Fix a mismatched comment in f2fs_shrink_count().
> 
> Signed-off-by: Chengguang Xu <cgxu519@zoho.com.cn>
> ---
>  fs/f2fs/shrinker.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/shrinker.c b/fs/f2fs/shrinker.c
> index a467aca29cfe..d66de5999a26 100644
> --- a/fs/f2fs/shrinker.c
> +++ b/fs/f2fs/shrinker.c
> @@ -58,7 +58,7 @@ unsigned long f2fs_shrink_count(struct shrinker *shrink,
>  		/* count extent cache entries */
>  		count += __count_extent_cache(sbi);
>  
> -		/* shrink clean nat cache entries */
> +		/* count clean nat cache entries */
>  		count += __count_nat_entries(sbi);
>  
>  		/* count free nids cache entries */
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2019-09-29  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28  1:40 [f2fs-dev] [PATCH] f2fs: fix a comment in f2fs_shrink_count() Chengguang Xu via Linux-f2fs-devel
2019-09-29  0:56 ` Chao Yu [this message]
2019-09-29  2:12   ` admin via Linux-f2fs-devel

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=0d773ecd-076e-54da-e952-8e6ad7894bb6@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=cgxu519@zoho.com.cn \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).