linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Jeffrey Lien <Jeff.Lien@wdc.com>
Cc: linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: NVMe CLI Doc Regen
Date: Thu, 19 Dec 2019 04:16:05 +0900	[thread overview]
Message-ID: <20191218191605.GA15983@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <BYAPR04MB5656D3C483431C89188A3C22EA530@BYAPR04MB5656.namprd04.prod.outlook.com>

On Wed, Dec 18, 2019 at 01:03:19AM +0000, Jeffrey Lien wrote:
> Keith,
> I added a new wdc plugin command (vs-telemetry-controller-option) in the last pull request and need the new doc files generated.  Could you do a regen of the Documentation files?  

Got it, new docs pushed now.

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      reply	other threads:[~2019-12-18 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18  1:03 NVMe CLI Doc Regen Jeffrey Lien
2019-12-18 19:16 ` Keith Busch [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=20191218191605.GA15983@redsun51.ssa.fujisawa.hgst.com \
    --to=kbusch@kernel.org \
    --cc=Jeff.Lien@wdc.com \
    --cc=linux-nvme@lists.infradead.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).