diff options
| author | Dan Williams <[email protected]> | 2016-04-14 19:40:47 -0700 |
|---|---|---|
| committer | Ross Zwisler <[email protected]> | 2016-04-15 14:59:41 -0600 |
| commit | 0a370d261c805286cbdfa1f96661322a28cce860 (patch) | |
| tree | 11035c733e2e9b0d6e33f181ae9b99aba22a3fac /net/lapb/lapb_in.c | |
| parent | cba2e47abcbd80e3f46f460899290402f98090ec (diff) | |
libnvdimm, pmem: clarify the write+clear_poison+write flow
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.
Reported-by: Jeff Moyer <[email protected]>
Reported-by: Vishal Verma <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Signed-off-by: Ross Zwisler <[email protected]>
Reviewed-by: Johannes Thumshirn <[email protected]>
Reviewed-by: Jeff Moyer <[email protected]>
Reviewed-by: Vishal Verma <[email protected]>
Diffstat (limited to 'net/lapb/lapb_in.c')
0 files changed, 0 insertions, 0 deletions