From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [ndctl PATCH] Documentation: add a newline in namespace Theory of Operations
Date: Wed, 27 Jun 2018 16:23:46 -0600 [thread overview]
Message-ID: <20180627222346.GB9504@linux.intel.com> (raw)
In-Reply-To: <20180627221543.23586-1-vishal.l.verma@intel.com>
On Wed, Jun 27, 2018 at 04:15:43PM -0600, Vishal Verma wrote:
> The first bullet in the modes description was merged in with the
> previous paragraph in the online version of the man pages. Fix by adding
> a newline before the bulleted list.
>
> Reported-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> ---
> Documentation/ndctl/namespace-description.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/ndctl/namespace-description.txt b/Documentation/ndctl/namespace-description.txt
> index 1dd687e..94999e5 100644
> --- a/Documentation/ndctl/namespace-description.txt
> +++ b/Documentation/ndctl/namespace-description.txt
> @@ -21,6 +21,7 @@ area.
> A namespace can be provisioned to operate in one of 4 modes, 'fsdax',
> 'devdax', 'sector', and 'raw'. Here are the expected usage models for
> these modes:
> +
> - fsdax: Filesystem-DAX mode is the default mode of a namespace
> when specifying 'ndctl create-namespace' with no options. It creates
> a block device (/dev/pmemX[.Y]) that supports the DAX capabilities
Cool, thanks for fixing.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2018-06-27 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 22:15 [ndctl PATCH] Documentation: add a newline in namespace Theory of Operations Vishal Verma
2018-06-27 22:23 ` Ross Zwisler [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=20180627222346.GB9504@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=vishal.l.verma@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 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.