From: thomas.tai@oracle.com (Thomas Tai)
Subject: [PATCH v4 0/2] nvme: Add fault injection feature
Date: Mon, 12 Feb 2018 11:46:48 -0500 [thread overview]
Message-ID: <d56d5db5-9b97-76dc-d9d9-b1639e026e0c@oracle.com> (raw)
In-Reply-To: <afb37e41-ee51-f243-dbe9-a812ff00c791@grimberg.me>
On 2018-02-11 05:09 AM, Sagi Grimberg wrote:
> Thomas,
>
> Applied to nvme-4.17 with a slight conflict. Please make sure
> that its correct.
Thanks Sagi. I retest with nvme-4.17, it works fine. I spotted a typo in
the document and will send out the correction. Would you kindly merge
the correction for me? I apologize for any inconvenience this may have
caused.
Thank you,
Thomas
>
> thanks,
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2018-02-12 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 18:38 [PATCH v4 0/2] nvme: Add fault injection feature Thomas Tai
2018-02-08 18:38 ` [PATCH v4 1/2] " Thomas Tai
2018-02-08 18:38 ` [PATCH v4 2/2] Documentation: nvme: Documentation for nvme fault injection Thomas Tai
2018-02-11 10:09 ` [PATCH v4 0/2] nvme: Add fault injection feature Sagi Grimberg
2018-02-12 16:46 ` Thomas Tai [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=d56d5db5-9b97-76dc-d9d9-b1639e026e0c@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