From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH 1/2] ndctl: add warning about overwrite taking a long time
Date: Wed, 27 Mar 2019 17:09:47 +0000 [thread overview]
Message-ID: <61e1e7e305884330d7832f1acd7363b8059a2da9.camel@intel.com> (raw)
In-Reply-To: <155329861947.65870.13816593912382889728.stgit@djiang5-desk3.ch.intel.com>
On Fri, 2019-03-22 at 16:50 -0700, Dave Jiang wrote:
> Add warning note in man page that overwrite may take a long time to
> execute.
>
> Suggested-by: Robert Elliot <elliott@hpe.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ndctl/ndctl-sanitize-dimm.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Both patches look good, applied. Thanks!
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2019-03-27 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 23:50 [PATCH 1/2] ndctl: add warning about overwrite taking a long time Dave Jiang
2019-03-22 23:50 ` [PATCH 2/2] ndctl: fix typo mistake for ndctl-sanitize-dimm Dave Jiang
2019-03-27 17:09 ` Verma, Vishal L [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=61e1e7e305884330d7832f1acd7363b8059a2da9.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-nvdimm@lists.01.org \
/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;
as well as URLs for NNTP newsgroup(s).