From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 6/8] ndctl/test: add a new unit test for inject-error
Date: Mon, 9 Oct 2017 23:49:51 +0000 [thread overview]
Message-ID: <1507592867.23025.81.camel@intel.com> (raw)
In-Reply-To: <20171006015405.29908-7-vishal.l.verma@intel.com>
On Thu, 2017-10-05 at 19:54 -0600, Vishal Verma wrote:
> +do_tests()
> +{
> + # TODO
> + return
> +}
Not sure how this happened, but I managed to include a stale version of
this file or something, that only has the boilerplate. I'll fix up for
the next rev.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-10-09 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 1:53 [ndctl PATCH 0/8] add an inject-error command to ndctl Vishal Verma
2017-10-06 1:53 ` [ndctl PATCH 1/8] libndctl: fix a memory leak in add_bus Vishal Verma
2017-10-07 15:44 ` Dan Williams
2017-10-06 1:53 ` [ndctl PATCH 2/8] ndctl, list: move the --human description to an include Vishal Verma
2017-10-07 15:55 ` Dan Williams
2017-10-06 1:54 ` [ndctl PATCH 3/8] libndctl: add APIs to get scrub count and to wait for a scrub Vishal Verma
2017-10-07 16:11 ` Dan Williams
2017-10-06 1:54 ` [ndctl PATCH 4/8] ccan/list: add a list_add_after helper Vishal Verma
2017-10-06 17:39 ` Dan Williams
2017-10-06 1:54 ` [ndctl PATCH 5/8] ndctl: add an inject-error command Vishal Verma
2017-10-09 16:27 ` Dan Williams
2017-10-06 1:54 ` [ndctl PATCH 6/8] ndctl/test: add a new unit test for inject-error Vishal Verma
2017-10-09 23:49 ` Verma, Vishal L [this message]
2017-10-06 1:54 ` [ndctl PATCH 7/8] ndctl/test: update existing unit tests to use error-inject Vishal Verma
2017-10-06 1:54 ` [ndctl PATCH 8/8] ndctl/test: add a new unit test for BTT error clearing Vishal Verma
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=1507592867.23025.81.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=linux-nvdimm@lists.01.org \
/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