From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme-cli/format: use existing LBAF if none requested
Date: Tue, 14 Mar 2017 09:23:51 -0700 [thread overview]
Message-ID: <20170314162351.GA21130@infradead.org> (raw)
In-Reply-To: <1489506857-24366-1-git-send-email-keith.busch@intel.com>
This looks fine to me:
Reviewed-by: Christoph Hellwig <hch at lst.de>
Btw, we really should do something about the global format behavior
bits in FNA - if bit 0 or 1 are set we should fail formats that
are specific to a namespace and not global with a warnings.
prev parent reply other threads:[~2017-03-14 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 15:54 [PATCH] nvme-cli/format: use existing LBAF if none requested Keith Busch
2017-03-14 16:23 ` Christoph Hellwig [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=20170314162351.GA21130@infradead.org \
--to=hch@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).