From mboxrd@z Thu Jan 1 00:00:00 1970 From: thomas.tai@oracle.com (Thomas Tai) Date: Thu, 8 Feb 2018 11:08:42 -0500 Subject: [PATCH v3 2/2] Documentation: nvme: Documentation for nvme fault injection In-Reply-To: References: <1517526659-3450-1-git-send-email-thomas.tai@oracle.com> <1517526659-3450-3-git-send-email-thomas.tai@oracle.com> <75fba2c9-3fb6-0cf8-fcf4-7738bd7c6147@grimberg.me> <600bfddd-448c-bedd-ba6c-a3e925137ee8@oracle.com> Message-ID: <483b49dc-a89c-cba7-3f63-9a29420e4b6c@oracle.com> On 2018-02-08 11:05 AM, Sagi Grimberg wrote: > >>>> +o NVMe fault injection >>>> + >>>> +? inject NVMe NVME_SC_INVALID_OPCODE with no retry on devices >>>> permitted >>>> +? by setting debugfs entries under >>>> /sys/kernel/debug/nvme*/fault_inject >>>> + >>> >>> Actually, can you update the documentation entry here? >> >> Yes Sagi. I will submit the documentation to the fault injection >> maintainer. Thank you for your help. > > 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?