From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] f2fs: don't pass a bio to f2fs_target_device
Date: Wed, 9 Mar 2022 13:56:01 -0800 [thread overview]
Message-ID: <YikiceholHfw3Vql@google.com> (raw)
In-Reply-To: <32114417-fd17-9412-28da-10f0ff09530d@kernel.org>
On 03/01, Chao Yu wrote:
> On 2022/2/28 20:41, Christoph Hellwig wrote:
> > Set the bdev at bio allocation time by changing the f2fs_target_device
> > calling conventions, so that no bio needs to be passed in.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Reviewed-by: Chao Yu <chao@kernel.org>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: don't pass a bio to f2fs_target_device
Date: Wed, 9 Mar 2022 13:56:01 -0800 [thread overview]
Message-ID: <YikiceholHfw3Vql@google.com> (raw)
In-Reply-To: <32114417-fd17-9412-28da-10f0ff09530d@kernel.org>
On 03/01, Chao Yu wrote:
> On 2022/2/28 20:41, Christoph Hellwig wrote:
> > Set the bdev at bio allocation time by changing the f2fs_target_device
> > calling conventions, so that no bio needs to be passed in.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Reviewed-by: Chao Yu <chao@kernel.org>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> Thanks,
_______________________________________________
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 21:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:41 fully convert f2fs to the new bio allocation interface Christoph Hellwig
2022-02-28 12:41 ` [f2fs-dev] " Christoph Hellwig
2022-02-28 12:41 ` [PATCH 1/2] f2fs: don't pass a bio to f2fs_target_device Christoph Hellwig
2022-02-28 12:41 ` [f2fs-dev] " Christoph Hellwig
2022-03-01 2:48 ` Chao Yu
2022-03-01 2:48 ` [f2fs-dev] " Chao Yu
2022-03-09 21:56 ` Jaegeuk Kim [this message]
2022-03-09 21:56 ` Jaegeuk Kim
2022-02-28 12:41 ` [PATCH 2/2] f2fs: pass the bio operation to bio_alloc_bioset Christoph Hellwig
2022-02-28 12:41 ` [f2fs-dev] " Christoph Hellwig
2022-03-01 2:49 ` Chao Yu
2022-03-01 2:49 ` [f2fs-dev] " Chao Yu
2022-03-08 6:06 ` Christoph Hellwig
2022-03-08 6:06 ` [f2fs-dev] " Christoph Hellwig
2022-03-09 0:59 ` Jens Axboe
2022-03-09 0:59 ` [f2fs-dev] " Jens Axboe
2022-03-09 22:03 ` Jaegeuk Kim
2022-03-09 22:03 ` [f2fs-dev] " Jaegeuk Kim
2022-03-09 22:02 ` Jaegeuk Kim
2022-03-09 22:02 ` [f2fs-dev] " 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=YikiceholHfw3Vql@google.com \
--to=jaegeuk@kernel.org \
--cc=axboe@kernel.dk \
--cc=chao@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.