From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 1/6] f2fs: use f2fs_io_info to clean up messy parameters during IO path
Date: Tue, 23 Dec 2014 15:00:24 +0800 [thread overview]
Message-ID: <003101d01e7e$3cb6a620$b623f260$@samsung.com> (raw)
In-Reply-To: <1419179723-3234-1-git-send-email-jaegeuk@kernel.org>
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Monday, December 22, 2014 12:35 AM
> To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> linux-f2fs-devel@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 1/6] f2fs: use f2fs_io_info to clean up messy parameters during IO
> path
>
> This patch cleans up parameters on IO paths.
> The key idea is to use f2fs_io_info adding a parameter, block address, and then
> use this structure as parameters.
>
Nice clean work.
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
prev parent reply other threads:[~2014-12-23 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 16:35 [PATCH 1/6] f2fs: use f2fs_io_info to clean up messy parameters during IO path Jaegeuk Kim
2014-12-21 16:35 ` [PATCH 2/6] f2fs: add f2fs_io_tracer support Jaegeuk Kim
2014-12-21 16:35 ` [PATCH 3/6] f2fs: add key functions for f2fs_io_tracer Jaegeuk Kim
2014-12-21 16:35 ` [PATCH 4/6] f2fs: activate f2fs_trace_pid Jaegeuk Kim
2014-12-21 16:35 ` [PATCH 5/6] f2fs: activate f2fs_trace_ios Jaegeuk Kim
2014-12-21 16:35 ` [PATCH 6/6] f2fs: avoid double lock for cp_rwsem Jaegeuk Kim
2014-12-23 7:01 ` [f2fs-dev] " Chao Yu
2014-12-23 7:40 ` Jaegeuk Kim
2014-12-23 8:58 ` Chao Yu
2014-12-23 19:05 ` Jaegeuk Kim
2014-12-23 19:08 ` [f2fs-dev] [PATCH 6/6 v2] " Jaegeuk Kim
2014-12-23 7:00 ` Chao Yu [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='003101d01e7e$3cb6a620$b623f260$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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).