From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] f2fs: reset iostat_count in f2fs_reset_iostat()
Date: Thu, 12 Jan 2023 15:59:17 -0800 [thread overview]
Message-ID: <Y8Ce1XO0Qeo8AnHh@google.com> (raw)
In-Reply-To: <20230112151328.29124-1-frank.li@vivo.com>
On 01/12, Yangtao Li wrote:
> Dear Jaegeuk,
>
> > Hi Yangtao,
> >
> > These are all in dev-test branch, which means you don't need to stack up more
> > patches on top of it. I just integrated most of them into two original patches.
>
> Ok, I'll merge the previous commits and resend next time.
>
> > Could you please take a look at this?
>
> LGTM.
>
> > Applied with the fix.
>
> Thanks!
>
> BTW, I would like to ask whether it is possible to maintain discard in separated file.
>
> https://patchwork.kernel.org/project/f2fs/patch/20221217132318.37718-1-frank.li@vivo.com/
Not worth.
>
> MBR,
> Yangtao
prev parent reply other threads:[~2023-01-12 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 11:21 [PATCH 1/4] f2fs: reset iostat_count in f2fs_reset_iostat() Yangtao Li
2023-01-04 11:21 ` [PATCH 2/4] f2fs: no need to call ktime_get_real_seconds() if iostat is not enabled Yangtao Li
2023-01-04 11:21 ` [PATCH 3/4] f2fs: introduce IOSTAT_INFO_SHOW macro Yangtao Li
2023-01-04 11:21 ` [PATCH 4/4] f2fs: rename rw_iostat to iostat_bytes Yangtao Li
2023-01-04 19:20 ` [PATCH 1/4] f2fs: reset iostat_count in f2fs_reset_iostat() Jaegeuk Kim
2023-01-11 14:06 ` Chao Yu
2023-01-11 19:17 ` Jaegeuk Kim
2023-01-12 15:13 ` Yangtao Li
2023-01-12 23:59 ` Jaegeuk Kim [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=Y8Ce1XO0Qeo8AnHh@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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