From: Dave Jiang <dave.jiang@intel.com>
To: Yi Zhang <yi.zhang@redhat.com>, nvdimm@lists.linux.dev
Cc: vishal.l.verma@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH ndctl] typo fix: ovewrite -> overwrite
Date: Tue, 9 May 2023 10:45:57 -0700 [thread overview]
Message-ID: <8fac1e26-2291-af82-323b-9e17ef7dd511@intel.com> (raw)
In-Reply-To: <20230509230005.2122950-1-yi.zhang@redhat.com>
On 5/9/23 4:00 PM, Yi Zhang wrote:
> Fix typos in Documentation/ndctl/ndctl-sanitize-dimm.txt and ndctl/lib/dimm.c
>
> Signed-off-by: Yi Zhang <yi.zhang@redhat.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ndctl/ndctl-sanitize-dimm.txt | 2 +-
> ndctl/lib/dimm.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/ndctl/ndctl-sanitize-dimm.txt b/Documentation/ndctl/ndctl-sanitize-dimm.txt
> index e044678..72ec96e 100644
> --- a/Documentation/ndctl/ndctl-sanitize-dimm.txt
> +++ b/Documentation/ndctl/ndctl-sanitize-dimm.txt
> @@ -47,7 +47,7 @@ include::xable-bus-options.txt[]
> label data. Namespaces get reverted to raw mode.
>
> -o::
> ---ovewrite::
> +--overwrite::
> Wipe the entire DIMM, including label data. This can take significant
> time, and the command is non-blocking. With this option, the overwrite
> request is merely submitted to the NVDIMM, and the completion is
> diff --git a/ndctl/lib/dimm.c b/ndctl/lib/dimm.c
> index 2b6e8a5..f9dde2f 100644
> --- a/ndctl/lib/dimm.c
> +++ b/ndctl/lib/dimm.c
> @@ -853,7 +853,7 @@ NDCTL_EXPORT int ndctl_dimm_wait_overwrite(struct ndctl_dimm *dimm)
> dbg(ctx, "%s: overwrite complete\n",
> ndctl_dimm_get_devname(dimm));
> else if (rc == 0)
> - dbg(ctx, "%s: ovewrite skipped\n",
> + dbg(ctx, "%s: overwrite skipped\n",
> ndctl_dimm_get_devname(dimm));
> else
> dbg(ctx, "%s: overwrite error waiting for complete\n",
prev parent reply other threads:[~2023-05-09 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 23:00 [PATCH ndctl] typo fix: ovewrite -> overwrite Yi Zhang
2023-05-09 15:33 ` Minwoo Im
2023-05-09 17:45 ` Dave Jiang [this message]
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=8fac1e26-2291-af82-323b-9e17ef7dd511@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
--cc=yi.zhang@redhat.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