From: Christoph Hellwig <hch@lst.de>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
hca@linux.ibm.com, gor@linux.ibm.com, linux-s390@vger.kernel.org,
linux-block@vger.kernel.org,
Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH] s390/dcssblk:: don't call bio_split_to_limits
Date: Tue, 24 Jan 2023 14:45:17 +0100 [thread overview]
Message-ID: <20230124134517.GA26408@lst.de> (raw)
In-Reply-To: <Y8/gDgQfQA7++8tw@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
On Tue, Jan 24, 2023 at 02:41:34PM +0100, Alexander Gordeev wrote:
> If my understanding is correct that this change was as good as
> early as commit 54efd50bfd87 ("block: make generic_make_request
> handle arbitrarily sized bios") took place and simply fell into
> the second category?
Yes.
next prev parent reply other threads:[~2023-01-24 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 7:53 [PATCH] s390/dcssblk:: don't call bio_split_to_limits Christoph Hellwig
2023-01-24 13:41 ` Alexander Gordeev
2023-01-24 13:45 ` Christoph Hellwig [this message]
2023-01-24 18:22 ` Alexander Gordeev
2023-01-24 18:27 ` Jens Axboe
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=20230124134517.GA26408@lst.de \
--to=hch@lst.de \
--cc=agordeev@linux.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@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