Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751960AbcDOMcS (ORCPT ); Fri, 15 Apr 2016 08:32:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48416 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750716AbcDOMcR (ORCPT ); Fri, 15 Apr 2016 08:32:17 -0400 From: Jeff Moyer To: Dan Williams Cc: linux-nvdimm@ml01.01.org, Vishal Verma , linux-kernel@vger.kernel.org Subject: Re: [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow References: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Fri, 15 Apr 2016 08:32:15 -0400 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") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 395 Lines: 10 Dan Williams 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