From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: [PATCH v2] Support for write stream IDs Date: Tue, 5 May 2015 14:12:01 -0600 Message-ID: <55492411.1010806@fb.com> References: <1430856181-19568-1-git-send-email-axboe@fb.com> <20150505200757.GA23902@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , To: Christoph Hellwig Return-path: Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:39965 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbbEEUPV (ORCPT ); Tue, 5 May 2015 16:15:21 -0400 In-Reply-To: <20150505200757.GA23902@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 05/05/2015 02:07 PM, Christoph Hellwig wrote: > On Tue, May 05, 2015 at 02:02:54PM -0600, Jens Axboe wrote: >> Unless there are any grave concerns here, I'd like to merge this for >> 4.2. > > Without a driver implementing the feature I don't see any reason to even > consider merging it. We can't merge the NVMe bits until the proposal is included/finalized. But this is a problem. I don't want to add this to the Facebook kernel until we know the API is stable, while I have no problem adding experimental NVMe changes since those can be easily updated without impacting applications. The latter is not true for the user interface. -- Jens Axboe