From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support
Date: Wed, 9 Mar 2016 23:05:03 +0000 [thread overview]
Message-ID: <1457564698.4525.33.camel@intel.com> (raw)
In-Reply-To: <20160308224713.16298.33547.stgit@dwillia2-desk3.jf.intel.com>
On Tue, 2016-03-08 at 14:47 -0800, Dan Williams wrote:
> ACPI 6.1 introduces the ability to send "clear error" commands to the
> ACPI0012:00 device representing the root of an "nvdimm bus".
>
> Similar to relocating a bad block on a disk, this support clears
> media errors in response to a write.
>
> ---
>
> Dan Williams (3):
> nfit, libnvdimm: clear poison command support
> libnvdimm, pmem: fix kmap_atomic() leak in error path
> libnvdimm, pmem: clear poison on write
>
>
> arch/x86/include/asm/pmem.h | 5 +++
> drivers/acpi/nfit.c | 12 ++++++-
> drivers/nvdimm/bus.c | 65
> ++++++++++++++++++++++++++++++++++++++
> drivers/nvdimm/nd.h | 2 +
> drivers/nvdimm/pmem.c | 40 ++++++++++++++++++++---
> include/linux/pmem.h | 19 +++++++++++
> include/uapi/linux/ndctl.h | 13 ++++++++
> tools/testing/nvdimm/test/nfit.c | 29 +++++++++++++++++
> 8 files changed, 179 insertions(+), 6 deletions(-)
Except for the one comment in patch 1, this looks good to me!
For the series,
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
prev parent reply other threads:[~2016-03-09 23:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 22:47 [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support Dan Williams
2016-03-08 22:47 ` [PATCH 1/3] nfit, libnvdimm: clear poison command support Dan Williams
2016-03-09 23:03 ` Verma, Vishal L
2016-03-09 23:07 ` Dan Williams
2016-03-08 22:47 ` [PATCH 2/3] libnvdimm, pmem: fix kmap_atomic() leak in error path Dan Williams
2016-03-08 22:47 ` [PATCH 3/3] libnvdimm, pmem: clear poison on write Dan Williams
2016-03-11 0:39 ` Verma, Vishal L
2016-03-11 0:50 ` Dan Williams
2016-03-09 23:05 ` Verma, Vishal L [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=1457564698.4525.33.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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