From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Yangtao Li <frank.li@vivo.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: no need test opt for f2fs_issue_flush
Date: Mon, 19 Jun 2023 23:21:06 -0700 [thread overview]
Message-ID: <ZJFFUuB6EemEg/DH@google.com> (raw)
In-Reply-To: <5409930b-4379-b279-886b-a05149436a68@kernel.org>
On 06/19, Chao Yu wrote:
> On 2023/4/26 0:58, Yangtao Li wrote:
> > This information can now be obtained from the mount, and there isi
> > no need to print it out every time the trace event is triggered.
>
> It makes sense.
>
> Jaegeuk, is it intentional to print mount option in f2fs_issue_flush
> tracepoint?
I don't remember tho, do we have a strong reason to change the tracepoint?
>
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-06-20 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:58 [f2fs-dev] [PATCH] f2fs: no need test opt for f2fs_issue_flush Yangtao Li via Linux-f2fs-devel
2023-06-13 8:01 ` Yangtao Li via Linux-f2fs-devel
2023-06-19 5:20 ` Chao Yu
2023-06-20 6:21 ` 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=ZJFFUuB6EemEg/DH@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;
as well as URLs for NNTP newsgroup(s).