From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/1] nvme-pci: check that sqid match in nvme cqe
Date: Wed, 9 Jan 2019 19:35:35 +0100 [thread overview]
Message-ID: <20190109183535.GA22051@lst.de> (raw)
In-Reply-To: <20190109183521.GA21992@lst.de>
On Wed, Jan 09, 2019@07:35:21PM +0100, Christoph Hellwig wrote:
> Yes, but hardware that gets this wrong will just blow up and timeout
> anyway. I'm not sure this case is worth adding a special detetion
> in the slow path.
s/slow/fast/
prev parent reply other threads:[~2019-01-09 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 13:37 [PATCH 1/1] nvme-pci: check that sqid match in nvme cqe Max Gurtovoy
2019-01-04 18:13 ` Christoph Hellwig
2019-01-06 12:21 ` Max Gurtovoy
2019-01-09 18:35 ` Christoph Hellwig
2019-01-09 18:35 ` Christoph Hellwig [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=20190109183535.GA22051@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