From: Christoph Hellwig <hch@infradead.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Michael Kelley <mikelley@microsoft.com>,
kys@microsoft.com, martin.petersen@oracle.com,
longli@microsoft.com, wei.liu@kernel.org, jejb@linux.ibm.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi: storvsc: Enable scatterlist entry lengths > 4Kbytes
Date: Wed, 24 Feb 2021 15:52:41 +0000 [thread overview]
Message-ID: <20210224155241.GA2284544@infradead.org> (raw)
In-Reply-To: <874ki2yhzm.fsf@vitty.brq.redhat.com>
Shouldn't storvsc just use blk_queue_virt_boundary instead of all this
mess?
next prev parent reply other threads:[~2021-02-24 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:01 [PATCH 1/1] scsi: storvsc: Enable scatterlist entry lengths > 4Kbytes Michael Kelley
2021-02-23 14:30 ` Vitaly Kuznetsov
2021-02-23 22:01 ` Michael Kelley
2021-02-24 15:52 ` Christoph Hellwig [this message]
2021-02-24 17:03 ` Michael Kelley
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=20210224155241.GA2284544@infradead.org \
--to=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=martin.petersen@oracle.com \
--cc=mikelley@microsoft.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu@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