Mauro Carvalho Chehab mchehab+huawei@kernel.org writes:
There are some ABI documents that, while they don't generate any warnings, they have issues when parsed by get_abi.pl script on its output result.
Address them, in order to provide a clean output.
Signed-off-by: Mauro Carvalho Chehab mchehab+huawei@kernel.org
<snip>
diff --git a/Documentation/ABI/testing/sysfs-bus-papr-pmem b/Documentation/ABI/testing/sysfs-bus-papr-pmem index c1a67275c43f..8316c33862a0 100644 --- a/Documentation/ABI/testing/sysfs-bus-papr-pmem +++ b/Documentation/ABI/testing/sysfs-bus-papr-pmem @@ -11,19 +11,26 @@ Description: at 'Documentation/powerpc/papr_hcalls.rst' . Below are the flags reported in this sysfs file:
* "not_armed" : Indicates that NVDIMM contents will not
* "not_armed"
Indicates that NVDIMM contents will not survive a power cycle.
* "flush_fail" : Indicates that NVDIMM contents
* "flush_fail"
Indicates that NVDIMM contents couldn't be flushed during last shut-down event.
* "restore_fail": Indicates that NVDIMM contents
* "restore_fail"
Indicates that NVDIMM contents couldn't be restored during NVDIMM initialization.
* "encrypted" : NVDIMM contents are encrypted.
* "smart_notify": There is health event for the NVDIMM.
* "scrubbed" : Indicating that contents of the
* "encrypted"
NVDIMM contents are encrypted.
* "smart_notify"
There is health event for the NVDIMM.
* "scrubbed"
Indicating that contents of the NVDIMM have been scrubbed.
* "locked" : Indicating that NVDIMM contents cant
* "locked"
Indicating that NVDIMM contents cant be modified until next power cycle.
What: /sys/bus/nd/devices/nmemX/papr/perf_stats @@ -51,4 +58,4 @@ Description: * "MedWDur " : Media Write Duration * "CchRHCnt" : Cache Read Hit Count * "CchWHCnt" : Cache Write Hit Count
* "FastWCnt" : Fast Write Count
\ No newline at end of file
* "FastWCnt" : Fast Write Count
<snip>
Thanks,
I am fine with proposed changes to sysfs-bus-papr-pmem.
Acked-by: Vaibhav Jain vaibhav@linux.ibm.com # for sysfs-bus-papr-pmem