Noticed while reading the file. Signed-off-by: Davidlohr Bueso <[email protected]> --- Documentation/ndctl/intel-nvdimm-security.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/ndctl/intel-nvdimm-security.txt b/Documentation/ndctl/intel-nvdimm-security.txt index 88b305b81978..4ae7ed517279 100644 --- a/Documentation/ndctl/intel-nvdimm-security.txt +++ b/Documentation/ndctl/intel-nvdimm-security.txt @@ -4,7 +4,7 @@ THEORY OF OPERATION ------------------- The Intel Device Specific Methods (DSM) specification v1.7 and v1.8 [1] introduced the following security management operations: -enable passhprase, update passphrase, unlock DIMM, disable security, +enable passphrase, update passphrase, unlock DIMM, disable security, freeze security, secure (crypto) erase, overwrite, master passphrase enable, master passphrase update, and master passphrase secure erase. @@ -115,7 +115,7 @@ This is invoked using `--overwrite` option for ndctl 'sanitize-dimm'. The overwrite operation wipes the entire NVDIMM. The operation can take a significant amount of time. NOTE: When the command returns successfully, it just means overwrite has been successfully started, and not that the -overwrite is complete. Subsequently, 'ndctl wait-overwrite'can be used +overwrite is complete. Subsequently, 'ndctl wait-overwrite' can be used to wait for the NVDIMMs that are performing overwrite. Upon successful completion of an overwrite, the WBINVD instruction is issued by the kernel. If both --crypto-erase and --overwrite options are supplied, then -- 2.41.0
