From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Jiang, Dave" <dave.jiang@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] ndctl: add options to update firmware manpage
Date: Fri, 2 Feb 2018 23:56:07 +0000 [thread overview]
Message-ID: <1517615766.8128.37.camel@intel.com> (raw)
In-Reply-To: <151761526035.7565.535231308729807997.stgit@djiang5-desk3.ch.intel.com>
On Fri, 2018-02-02 at 16:47 -0700, Dave Jiang wrote:
> update firmware is missing the long/short option in the manpage.
> Adding
> the missing sections.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ndctl/ndctl-update-firmware.txt | 17
> +++++++++++++++++
> 1 file changed, 17 insertions(+)
Looks good, I have folded it in to the original patch.
>
> diff --git a/Documentation/ndctl/ndctl-update-firmware.txt
> b/Documentation/ndctl/ndctl-update-firmware.txt
> index d742302..dd90612 100644
> --- a/Documentation/ndctl/ndctl-update-firmware.txt
> +++ b/Documentation/ndctl/ndctl-update-firmware.txt
> @@ -10,6 +10,23 @@ SYNOPSIS
> [verse]
> 'ndctl update-firmware' -f <firmware_file> -d <dimm name>
>
> +EXAMPLES
> +--------
> +
> +Updating DIMM nmem0 with firmware file name firmwarefile.bin.
> +[verse]
> +ndctl update-firmware -f firmwarefile.bin -d nmem0
> +
> +OPTIONS
> +-------
> +-f::
> +--firmware=::
> + The path and name of the firmware file to be updated.
> +
> +-d::
> +--dimm=::
> + The DIMM name to be updated.
> +
> COPYRIGHT
> ---------
> Copyright (c) 2016 - 2017, Intel Corporation. License GPLv2: GNU GPL
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2018-02-02 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 23:47 [PATCH] ndctl: add options to update firmware manpage Dave Jiang
2018-02-02 23:56 ` 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=1517615766.8128.37.camel@intel.com \
--to=vishal.l.verma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.