From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places
Date: Mon, 9 Apr 2018 17:07:30 -0600 [thread overview]
Message-ID: <20180409230730.GA20234@linux.intel.com> (raw)
In-Reply-To: <CAPcyv4ho-K3MMOn+mJ5JEcE1_C0CErGL2KY04-hTcPn2GNyGmw@mail.gmail.com>
On Mon, Apr 09, 2018 at 03:10:26PM -0700, Dan Williams wrote:
> On Mon, Apr 9, 2018 at 1:09 PM, Ross Zwisler
> <ross.zwisler@linux.intel.com> wrote:
> > Adding on to the work started by:
> >
> > commit ebb4fb605e68 ("ndctl, create-namespace: introduce "fsdax" and "devdax" modes")
>
> I'd say "why" here.
Because having both "memory" and "fsdax" and having to know that they are
aliases is confusing. It'd be great if we could just choose one term and
stick with it, and I thought the term we had decided on was "fsdax".
> Also, might as well also convert util_namespace_to_json() to emit
> "fsdax" in all cases. I had initially thought there were compat
> concerns with removing the "memory" designation, but it will just
> cause ongoing confusion. Lets kill its output everywhere, but of
> course still accept it as a command input.
Cool, I think that'd be best.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2018-04-09 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 20:09 [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places Ross Zwisler
2018-04-09 20:09 ` [ndctl PATCH 2/2] ndctl: fix some spelling mistakes Ross Zwisler
2018-04-09 20:34 ` Dan Williams
2018-04-09 22:10 ` [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places Dan Williams
2018-04-09 23:07 ` 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=20180409230730.GA20234@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=dan.j.williams@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.