From: thomas.tai@oracle.com (Thomas Tai)
Subject: [PATCH v3 2/2] Documentation: nvme: Documentation for nvme fault injection
Date: Thu, 8 Feb 2018 11:19:03 -0500 [thread overview]
Message-ID: <af2a15b1-8887-77ec-98b7-abc9b630b47c@oracle.com> (raw)
In-Reply-To: <2c1534d4-c2c8-3e38-59bb-170c7c3d205a@grimberg.me>
[ ... ]
>>> It's going to 4.17 (we have time), so I'd prefer to get it right once
>>> instead of having another fixup on top. Would it be possible to re-spin
>>> with the minor fix?
>>
>> Sure. Do you mean I should resend the patch set which include the
>> fault injection maintainer in the email?
>
> No, just fix the documentation to say not only NVME_SC_INVALID_OPCODE
> can be injected (the entry in fault-injection.txt)
Oh yes. Sorry I missed that. will update the doc. Thank you.
next prev parent reply other threads:[~2018-02-08 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 23:10 [PATCH v3 0/2] nvme: Add fault injection feature Thomas Tai
2018-02-01 23:10 ` [PATCH v3 1/2] " Thomas Tai
2018-02-07 23:46 ` Keith Busch
2018-02-08 14:13 ` Thomas Tai
2018-02-01 23:10 ` [PATCH v3 2/2] Documentation: nvme: Documentation for nvme fault injection Thomas Tai
2018-02-07 23:50 ` Keith Busch
2018-02-08 14:14 ` Thomas Tai
2018-02-08 15:31 ` Sagi Grimberg
2018-02-08 15:42 ` Sagi Grimberg
2018-02-08 16:03 ` Thomas Tai
2018-02-08 16:05 ` Sagi Grimberg
2018-02-08 16:08 ` Thomas Tai
2018-02-08 16:17 ` Sagi Grimberg
2018-02-08 16:19 ` Thomas Tai [this message]
2018-02-05 14:49 ` [PATCH v3 0/2] nvme: Add fault injection feature Sagi Grimberg
2018-02-07 20:03 ` Thomas Tai
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=af2a15b1-8887-77ec-98b7-abc9b630b47c@oracle.com \
--to=thomas.tai@oracle.com \
/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