From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices Date: Tue, 23 Jun 2015 12:20:08 +0200 Message-ID: <20150623102008.GH24894@lst.de> References: <20150617235209.12943.24419.stgit@dwillia2-desk3.amr.corp.intel.com> <20150617235458.12943.23425.stgit@dwillia2-desk3.amr.corp.intel.com> <20150622163453.GA9187@lst.de> <20150622164837.GB9393@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dan Williams , Christoph Hellwig , Jens Axboe , "linux-nvdimm@lists.01.org" , Neil Brown , Greg KH , "linux-kernel@vger.kernel.org" , Ingo Molnar , Linux ACPI , linux-fsdevel To: Jeff Moyer Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jun 22, 2015 at 03:09:02PM -0400, Jeff Moyer wrote: > The xfs example is enough to convince me that we need to support btt on > a partition right now. Otherwise, for RHEL at least, dax on xfs simply > won't be supported. Seems like an odd stance to support some new code coming out of the blue in favor of something developed by RH for years and already shipping as the default filesystem at the major competitor..