From: Christoph Hellwig <hch@infradead.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [PATCH] f2fs: change fiemap way in printing compression chunk
Date: Thu, 22 Jul 2021 07:24:46 +0100 [thread overview]
Message-ID: <YPkPLrBszwr1aiBe@infradead.org> (raw)
In-Reply-To: <20210721072048.3035928-1-daeho43@gmail.com>
Btw, any chane you could switch f2fs to use iomap_fiemap instead of
the handrolled version? Especially with the work from Eric to add
iomap based direct I/O this should be much simpler now.
next prev parent reply other threads:[~2021-07-22 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 7:20 [PATCH] f2fs: change fiemap way in printing compression chunk Daeho Jeong
2021-07-21 21:35 ` [f2fs-dev] " Eric Biggers
2021-07-21 22:30 ` Daeho Jeong
2021-07-22 0:15 ` Eric Biggers
2021-07-22 1:04 ` Daeho Jeong
2021-07-22 1:15 ` Eric Biggers
2021-07-22 1:40 ` Daeho Jeong
2021-07-22 1:56 ` Eric Biggers
2021-07-22 3:59 ` Daeho Jeong
2021-07-22 6:24 ` Christoph Hellwig [this message]
2021-07-22 6:39 ` Daeho Jeong
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=YPkPLrBszwr1aiBe@infradead.org \
--to=hch@infradead.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.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).