All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>, Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] f2fs: pass the bio operation to bio_alloc_bioset
Date: Tue, 8 Mar 2022 17:59:40 -0700	[thread overview]
Message-ID: <779bf1fe-7f58-51ed-27e8-1152375780ff@kernel.dk> (raw)
In-Reply-To: <20220308060624.GA23629@lst.de>

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.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>, Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: pass the bio operation to bio_alloc_bioset
Date: Tue, 8 Mar 2022 17:59:40 -0700	[thread overview]
Message-ID: <779bf1fe-7f58-51ed-27e8-1152375780ff@kernel.dk> (raw)
In-Reply-To: <20220308060624.GA23629@lst.de>

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.

-- 
Jens Axboe



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2022-03-09  1:15 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
2022-03-09 21:56       ` [f2fs-dev] " 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 [this message]
2022-03-09  0:59         ` 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=779bf1fe-7f58-51ed-27e8-1152375780ff@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chao@kernel.org \
    --cc=hch@lst.de \
    --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 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.