NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: vishal.l.verma@intel.com
Cc: dave.jiang@intel.com, nvdimm@lists.linux.dev, dave@stgolabs.net
Subject: [ndctl PATCH] ndctl/security: fix Theory of Operation typos
Date: Mon, 24 Jul 2023 18:54:57 -0700	[thread overview]
Message-ID: <20230725015457.31084-1-dave@stgolabs.net> (raw)

Noticed while reading the file.

Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
---
 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


             reply	other threads:[~2023-07-25  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  1:54 Davidlohr Bueso [this message]
2023-07-25 15:14 ` [ndctl PATCH] ndctl/security: fix Theory of Operation typos Dave Jiang

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=20230725015457.31084-1-dave@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=dave.jiang@intel.com \
    --cc=nvdimm@lists.linux.dev \
    --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