From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cn.fujitsu.com ([59.151.112.132]:1435 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752210AbcDACCD (ORCPT ); Thu, 31 Mar 2016 22:02:03 -0400 Subject: Re: [PATCH v9 00/19] Btrfs dedupe framework To: , , References: <1459324574-28063-1-git-send-email-quwenruo@cn.fujitsu.com> <20160331161201.GD6230@twin.jikos.cz> From: Qu Wenruo Message-ID: <56FDD693.2020508@cn.fujitsu.com> Date: Fri, 1 Apr 2016 10:01:55 +0800 MIME-Version: 1.0 In-Reply-To: <20160331161201.GD6230@twin.jikos.cz> Content-Type: text/plain; charset="utf-8"; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: David Sterba wrote on 2016/03/31 18:12 +0200: > On Wed, Mar 30, 2016 at 03:55:55PM +0800, Qu Wenruo wrote: >> This March 30th patchset update mostly addresses the patchset structure >> comment from David: >> 1) Change the patchset sequence >> Not If only apply the first 14 patches, it can provide the full >> backward compatible in-memory only dedupe backend. >> >> Only starts from patch 15, on-disk format will be changed. >> >> So patch 1~14 is going to be pushed for next merge window, while I'll >> still submit them all for review purpose. > > I'll buy 1-10 with the ioctl hidden under the BTRFS_DEBUG config option > until the interface is settled. > > BTW, don't pick them directly, as I just forgot independent 2 bug fix patches. Thanks, Qu