From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices Date: Wed, 24 Jun 2015 14:10:40 +0200 Message-ID: <20150624121040.GB17542@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> <20150623101917.GG24894@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.211]:50676 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751493AbbFXMKm (ORCPT ); Wed, 24 Jun 2015 08:10:42 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Dan Williams Cc: Christoph Hellwig , Jeff Moyer , Jens Axboe , "linux-nvdimm@lists.01.org" , Neil Brown , Greg KH , "linux-kernel@vger.kernel.org" , Ingo Molnar , Linux ACPI , linux-fsdevel On Tue, Jun 23, 2015 at 08:19:57AM -0700, Dan Williams wrote: > That tie was only to enable autodetect so that we don't need to run a > BTT assembly step from an initramfs just to get an NVDIMM up and > running. It was a convenience, not a requirement. It's a very deep tying for that feature. Look at what the raid code does just for scanning. Although even that is officially deprecate because people don't like in-kernel scanning (which I tend to disagree with).