From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: bio splitting cleanups v2
Date: Tue, 26 Jul 2022 12:22:05 -0600 [thread overview]
Message-ID: <16f5d4bd-283d-9622-8da7-ec8a9ee7048a@kernel.dk> (raw)
In-Reply-To: <20220726110511.GB30558@lst.de>
On 7/26/22 5:05 AM, Christoph Hellwig wrote:
> On Mon, Jul 25, 2022 at 05:06:19PM -0600, Jens Axboe wrote:
>> Since this clashes with opf changes from Bart, would you mind spinning
>> them against the for-5.20/drivers-post branch?
>
> Actually. The conflict seems to be that for-5.20/drivers-post still
> has the blkcg_bio_issue_init in __blk_queue_split that went away
> in for-5.20/block. So while I can resend against drivers-post, that
> seems somewhat counterproductive.
Can you make sure the series applies to my for-next? Then I'll create a
temp branch for it.
--
Jens Axboe
prev parent reply other threads:[~2022-07-26 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 6:28 bio splitting cleanups v2 Christoph Hellwig
2022-07-23 6:28 ` [PATCH 1/6] block: change the blk_queue_split calling convention Christoph Hellwig
2022-07-23 6:28 ` [PATCH 2/6] block: change the blk_queue_bounce " Christoph Hellwig
2022-07-23 6:28 ` [PATCH 3/6] block: move ->bio_split to the gendisk Christoph Hellwig
2022-07-23 6:28 ` [PATCH 4/6] block: move the call to get_max_io_size out of blk_bio_segment_split Christoph Hellwig
2022-07-23 6:28 ` [PATCH 5/6] block: move bio_allowed_max_sectors to blk-merge.c Christoph Hellwig
2022-07-23 6:28 ` [PATCH 6/6] block: pass struct queue_limits to the bio splitting helpers Christoph Hellwig
2022-07-25 23:06 ` bio splitting cleanups v2 Jens Axboe
2022-07-26 11:05 ` Christoph Hellwig
2022-07-26 18:22 ` Jens Axboe [this message]
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=16f5d4bd-283d-9622-8da7-ec8a9ee7048a@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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.