From: Christoph Hellwig <hch@lst.de>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] fully convert f2fs to the new bio allocation interface
Date: Mon, 28 Feb 2022 14:41:21 +0200 [thread overview]
Message-ID: <20220228124123.856027-1-hch@lst.de> (raw)
Hi Jaegeuk and Chao,
as of the for-5.18/block tree, the bio allocation interfaces expect the
block_device and operation passed. This fixes f2fs up to match that
scheme.
It could go into Jens' alloc-cleanups branch if there are no conflicts
in the f2fs tree.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2022-02-28 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:41 Christoph Hellwig [this message]
2022-02-28 12:41 ` [f2fs-dev] [PATCH 1/2] f2fs: don't pass a bio to f2fs_target_device Christoph Hellwig
2022-03-01 2:48 ` Chao Yu
2022-03-09 21:56 ` Jaegeuk Kim
2022-02-28 12:41 ` [f2fs-dev] [PATCH 2/2] f2fs: pass the bio operation to bio_alloc_bioset Christoph Hellwig
2022-03-01 2:49 ` Chao Yu
2022-03-08 6:06 ` Christoph Hellwig
2022-03-09 0:59 ` Jens Axboe
2022-03-09 22:03 ` Jaegeuk Kim
2022-03-09 22:02 ` Jaegeuk Kim
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=20220228124123.856027-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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).