From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux@roeck-us.net, James.Bottomley@HansenPartnership.com,
linux-block@vger.kernel.org
Subject: Re: [PATCH] block: fix max segment size handling in blk_queue_virt_boundary
Date: Fri, 26 Jul 2019 12:52:38 -0600 [thread overview]
Message-ID: <e112ef7e-e1c4-ac62-367a-dfc0cc6e1c58@kernel.dk> (raw)
In-Reply-To: <20190726073518.GA23993@lst.de>
On 7/26/19 1:35 AM, Christoph Hellwig wrote:
> Jens, can you take a look? This fixes a boot regression hitting
> various people.
Sorry, totally missed this... Did already send in a pull request
today, but I'll get this applied and out before -rc2.
--
Jens Axboe
prev parent reply other threads:[~2019-07-26 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 16:26 [PATCH] block: fix max segment size handling in blk_queue_virt_boundary Christoph Hellwig
2019-07-25 0:31 ` Bob Liu
2019-07-26 7:35 ` Christoph Hellwig
2019-07-26 18:52 ` 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=e112ef7e-e1c4-ac62-367a-dfc0cc6e1c58@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).