Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH V2 0/3] nvme-cli: update Firmware Activate to Firmware Commit
Date: Tue, 19 Dec 2017 13:19:59 -0700	[thread overview]
Message-ID: <20171219201959.GA23384@localhost.localdomain> (raw)
In-Reply-To: <1513504682-30766-1-git-send-email-minwoo.im.dev@gmail.com>

On Sun, Dec 17, 2017@06:58:02PM +0900, Minwoo Im wrote:
> This patch set will make it support alias of every subcommands in nvme-cli.
> To show how this is done, update "Firmware Activate" command to
> "Firmware Commit" by making it as an alias.
> Also it updates "Firmware Commit" command to support boot partition feature
> which was introduced in NVMe 1.3 spec.
> 
> Please feel free to give feedbacks and reviews.
> 
> Changes to V1:
> - add support alias infrastructure for subcommands (Keith)

Thanks, this all looks good to me. Applied.

      reply	other threads:[~2017-12-19 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17  9:58 [PATCH V2 0/3] nvme-cli: update Firmware Activate to Firmware Commit Minwoo Im
2017-12-19 20:19 ` 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=20171219201959.GA23384@localhost.localdomain \
    --to=keith.busch@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