From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: pass the bio operation to bio_alloc_bioset
Date: Wed, 9 Mar 2022 14:03:58 -0800 [thread overview]
Message-ID: <YikkTgK7aXvONopy@google.com> (raw)
In-Reply-To: <779bf1fe-7f58-51ed-27e8-1152375780ff@kernel.dk>
Hi Jens,
On 03/08, Jens Axboe wrote:
> On 3/7/22 11:06 PM, Christoph Hellwig wrote:
> > On Tue, Mar 01, 2022 at 10:49:06AM +0800, Chao Yu wrote:
> >> On 2022/2/28 20:41, Christoph Hellwig wrote:
> >>> Refactor block I/O code so that the bio operation and known flags are set
> >>> at bio allocation time. Only the later updated flags are updated on the
> >>> fly.
> >>>
> >>> Signed-off-by: Christoph Hellwig <hch@lst.de>
> >>
> >> Reviewed-by: Chao Yu <chao@kernel.org>
> >
> > Is it okay for Jens to pick these two patches up in the
> > https://git.kernel.dk/cgit/linux-block/log/?h=for-5.18/alloc-cleanups
> > branch?
>
> I have tentatively done so, let me know you prefer doing it differently.
I've acked to the patches, and it seems they need to be landed in block.
Thank you.
>
> --
> Jens Axboe
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-03-09 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:41 [f2fs-dev] fully convert f2fs to the new bio allocation interface Christoph Hellwig
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 [this message]
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=YikkTgK7aXvONopy@google.com \
--to=jaegeuk@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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).