From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>, Jan Kara <jack@suse.com>,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/4] fs: remove generic_block_fiemap
Date: Mon, 26 Jul 2021 18:17:49 +0200 [thread overview]
Message-ID: <20210726161749.GI20621@quack2.suse.cz> (raw)
In-Reply-To: <20210726135459.GB8496@lst.de>
On Mon 26-07-21 15:54:59, Christoph Hellwig wrote:
> On Mon, Jul 26, 2021 at 03:52:56PM +0200, Jan Kara wrote:
> > On Tue 20-07-21 15:33:41, Christoph Hellwig wrote:
> > > Remove the now unused generic_block_fiemap helper.
> > >
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > Nice. Feel free to add:
> >
> > Reviewed-by: Jan Kara <jack@suse.cz>
>
> Do you just want to pick the whole series up through the ext2 tree?
Sure. I've queued it up (generic_block_fiemap removal branch, pulled in
for_next branch).
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-07-26 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 13:33 remove generic_block_fiemap Christoph Hellwig
2021-07-20 13:33 ` [PATCH 1/4] ext2: make ext2_iomap_ops available unconditionally Christoph Hellwig
2021-07-26 13:33 ` Jan Kara
2021-07-20 13:33 ` [PATCH 2/4] ext2: use iomap_fiemap to implement ->fiemap Christoph Hellwig
2021-07-26 13:41 ` Jan Kara
2021-07-20 13:33 ` [PATCH 3/4] hpfs: " Christoph Hellwig
2021-07-20 13:33 ` [PATCH 4/4] fs: remove generic_block_fiemap Christoph Hellwig
2021-07-26 13:52 ` Jan Kara
2021-07-26 13:54 ` Christoph Hellwig
2021-07-26 16:17 ` Jan Kara [this message]
2021-07-20 17:02 ` Mikulas Patocka
2021-07-21 5:37 ` Christoph Hellwig
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=20210726161749.GI20621@quack2.suse.cz \
--to=jack@suse.cz \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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).