From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 4A2D12267F105 for ; Mon, 9 Apr 2018 15:10:28 -0700 (PDT) Received: by mail-ot0-x22c.google.com with SMTP id f47-v6so10474835oth.2 for ; Mon, 09 Apr 2018 15:10:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180409200920.20177-1-ross.zwisler@linux.intel.com> References: <20180409200920.20177-1-ross.zwisler@linux.intel.com> From: Dan Williams Date: Mon, 9 Apr 2018 15:10:26 -0700 Message-ID: Subject: Re: [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Ross Zwisler Cc: linux-nvdimm List-ID: On Mon, Apr 9, 2018 at 1:09 PM, Ross Zwisler wrote: > Adding on to the work started by: > > commit ebb4fb605e68 ("ndctl, create-namespace: introduce "fsdax" and "devdax" modes") I'd say "why" here. 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. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm