From: Jeff Moyer <jmoyer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@ml01.01.org, Vishal Verma <vishal.l.verma@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow
Date: Fri, 15 Apr 2016 08:32:15 -0400 [thread overview]
Message-ID: <x49vb3j6oj4.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> (Dan Williams's message of "Thu, 14 Apr 2016 19:40:47 -0700")
Dan Williams <dan.j.williams@intel.com> writes:
> The ACPI specification does not specify the state of data after a clear
> poison operation. Potential future libnvdimm bus implementations for
> other architectures also might not specify or disagree on the state of
> data after clear poison. Clarify why we write twice.
Thanks, Dan, looks good.
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
next prev parent reply other threads:[~2016-04-15 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 2:40 Dan Williams
2016-04-15 7:11 ` Johannes Thumshirn
2016-04-15 12:32 ` Jeff Moyer [this message]
2016-04-15 16:58 ` Verma, Vishal L
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=x49vb3j6oj4.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=vishal.l.verma@intel.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
Powered by JetHome