Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752970AbcK2WeK (ORCPT ); Tue, 29 Nov 2016 17:34:10 -0500 Received: from mail-lf0-f66.google.com ([209.85.215.66]:34418 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751015AbcK2WeB (ORCPT ); Tue, 29 Nov 2016 17:34:01 -0500 MIME-Version: 1.0 In-Reply-To: <20161126201534.5d5e338f678b478e7a7b8dc3@gmail.com> References: <20161126201534.5d5e338f678b478e7a7b8dc3@gmail.com> From: Dan Streetman Date: Tue, 29 Nov 2016 17:33:19 -0500 X-Google-Sender-Auth: rJxd-4CQZakzvn2-1rQLzrSiGPA Message-ID: Subject: Re: [PATCH 0/2] z3fold fixes To: Vitaly Wool Cc: Linux-MM , linux-kernel , Andrew Morton , Arnd Bergmann , Dan Carpenter Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id uATMYFHJ001403 Content-Length: 868 Lines: 15 On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool wrote: > Here come 2 patches with z3fold fixes for chunks counting and locking. As commit 50a50d2 ("z3fold: don't fail kernel build is z3fold_header is too big") was NAK'ed [1], I would suggest that we removed that one and the next z3fold commit cc1e9c8 ("z3fold: discourage use of pages that weren't compacted") and applied the coming 2 instead. Instead of adding these onto all the previous ones, could you redo the entire z3fold series? I think it'll be simpler to review the series all at once and that would remove some of the stuff from previous patches that shouldn't be there. If that's ok with Andrew, of course, but I don't think any of the z3fold patches have been pushed to Linus yet. > > Signed-off-by: Vitaly Wool > > [1] https://lkml.org/lkml/2016/11/25/595