From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-pci: fix single segment detection
Date: Mon, 13 May 2019 08:26:15 +0200 [thread overview]
Message-ID: <20190513062615.GA18152@lst.de> (raw)
In-Reply-To: <20190509133120.GA22059@ming.t460p>
So actually, after running out ways to make any of my complex block
layer fix ideas work I have a simple fix for the block layer now.
Lets see if is acceptable..
next prev parent reply other threads:[~2019-05-13 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 11:04 [PATCH] nvme-pci: fix single segment detection Christoph Hellwig
2019-05-09 11:24 ` Ming Lei
2019-05-09 12:34 ` Christoph Hellwig
2019-05-09 13:31 ` Ming Lei
2019-05-13 6:26 ` Christoph Hellwig [this message]
2019-05-12 15:20 ` Sagi Grimberg
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=20190513062615.GA18152@lst.de \
--to=hch@lst.de \
/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