From: Vishal Verma <vishal.l.verma@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [ndctl PATCH 0/3] ndctl: nvdimm notification tests
Date: Tue, 23 Aug 2016 17:48:03 -0600 [thread overview]
Message-ID: <20160823234802.GD7799@omniknight.lm.intel.com> (raw)
In-Reply-To: <147199350116.5587.2852255825958647760.stgit@dwillia2-desk3.amr.corp.intel.com>
On 08/23, Dan Williams wrote:
> Add a new api, ndctl_dimm_get_health_eventfd(), and test that the kernel
> signals an event on that file descriptor after a smart-threshold
> command.
>
> Also, include a new gate for the SMART verification test to await when
> nfit_test is updated to emit the new v1.2 format of the SMART DSM
> payload.
>
> ---
>
> Dan Williams (3):
> test: gate SMART payload verification on v4.9
> ndctl: add ndctl_dimm_get_health_eventfd() api
> test: validate ndctl_dimm_get_health_eventfd()
>
>
> ndctl/lib/libndctl.c | 11 +++++++++
> ndctl/lib/libndctl.sym | 1 +
> ndctl/libndctl.h.in | 1 +
> test/libndctl.c | 61 ++++++++++++++++++++++++++++++++++++++++++++----
> 4 files changed, 69 insertions(+), 5 deletions(-)
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2016-08-23 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 23:05 [ndctl PATCH 0/3] ndctl: nvdimm notification tests Dan Williams
2016-08-23 23:05 ` [ndctl PATCH 1/3] test: gate SMART payload verification on v4.9 Dan Williams
2016-08-23 23:05 ` [ndctl PATCH 2/3] ndctl: add ndctl_dimm_get_health_eventfd() api Dan Williams
2016-08-23 23:05 ` [ndctl PATCH 3/3] test: validate ndctl_dimm_get_health_eventfd() Dan Williams
2016-08-23 23:48 ` Vishal Verma [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=20160823234802.GD7799@omniknight.lm.intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@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