From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 0/5] ahci: nvme remap support Date: Mon, 24 Oct 2016 20:21:36 +0200 Message-ID: <20161024182136.GA11822@lst.de> References: <147709592108.3733.7194541797066785254.stgit@dwillia2-desk3.amr.corp.intel.com> <20161022065038.GA8547@lst.de> <20161023083424.GA31994@lst.de> <20161024124938.GB2389@lst.de> <20161024144628.GC8633@localhost.localdomain> <20161024151657.GA7080@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.211]:39180 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936464AbcJXSVh (ORCPT ); Mon, 24 Oct 2016 14:21:37 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Dan Williams Cc: Christoph Hellwig , Keith Busch , Tejun Heo , IDE/ATA development list , linux-nvme@lists.infradead.org On Mon, Oct 24, 2016 at 10:57:16AM -0700, Dan Williams wrote: > ...but it still might be the better way to go. I.e. push the hacks to > the legacy driver and not burden nvme with this new "nvme_dev_ops" > concept. Let's get some coherent text on how this device even operates out first and then we can decide if and how we can support it.