Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp856511ybn; Wed, 2 Oct 2019 07:16:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwWO/KXr21FytbmEijV6jPlB031lSDE22VD77DycTaFDBsfW1wcAfWQKZXUd16pKMaOurNq X-Received: by 2002:aa7:d501:: with SMTP id y1mr3958949edq.226.1570025799171; Wed, 02 Oct 2019 07:16:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570025799; cv=none; d=google.com; s=arc-20160816; b=Zu0ET62xg9MqDWuaf7P8yEpUUYHKHC2A7OhLjbhclskgIvFzpVnNvT0RG85qAxXfAE 48xKLLROW5agXs20ZmcnklrcKD72wx/AT183YH+LoP1uYp3pdAraELAsUyP3CMwjPV0s K2/+Am9QldYSDzN3vpAt7U1MvoOExxVH9RGL0sVyYqxFLx/3vGWEqz3TOMJLM5/JLFQS ZwF6IKfkmTQ80eRQoJAY05lweRgZz/zQ2tMLV/0wdsGHhnlD5lbjGqCHG0iMc1jJURSj XFUGDuKPqqs+INuEZK/OyhfccnNRD7dbV6jKnNErXvHCAGqUWubzUUWvOQLNjd8cKR0K SMwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=JY8Aw3cu6UNhmNIsvq9Etb4yMdv3+pkFyvyRdaPMa9E=; b=svqezXb4e8IgutQzlqNBFj0iYa+WCAnsLSaaXZW1MURxdwtuK2EVN0uSo4KAvg+MwW UoJOvonRueTyL2uvtbqUOWn+2H2yHexErLnz+pulXaw1e940L2jARY97cejibmSXG0ZQ l7f0dIMTQ2HpD8K3C+ao+3mZU5YmB1r7B8M4n5lTKvRabLiuxl70DfwYy5d+Y/VicAxc XdRCLmQ3BIg+gEkvR2zroHrwSR8vzjZ7oAbbEcUsK/VJDwGuqzj4CLJ68N64PF5lKxKM +4Vd0G/Y462YNHClVua++4LTUGi2RjA/GLMrwFoyui8hAKeSqASnF0kGVeS2ZXPTcK1y XR6Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 20si10943658ejv.342.2019.10.02.07.16.10; Wed, 02 Oct 2019 07:16:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728022AbfJBOO5 (ORCPT + 99 others); Wed, 2 Oct 2019 10:14:57 -0400 Received: from mx2.suse.de ([195.135.220.15]:45256 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726200AbfJBOO4 (ORCPT ); Wed, 2 Oct 2019 10:14:56 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 0C248ACA4; Wed, 2 Oct 2019 14:14:55 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 3DEF4DA88C; Wed, 2 Oct 2019 16:15:12 +0200 (CEST) Date: Wed, 2 Oct 2019 16:15:12 +0200 From: David Sterba To: Tejun Heo Cc: dsterba@suse.cz, josef@toxicpanda.com, clm@fb.com, dsterba@suse.com, axboe@kernel.dk, jack@suse.cz, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCHSET v3 btrfs/for-next] btrfs: fix cgroup writeback support Message-ID: <20191002141512.GP2751@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Tejun Heo , josef@toxicpanda.com, clm@fb.com, dsterba@suse.com, axboe@kernel.dk, jack@suse.cz, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, kernel-team@fb.com References: <20190710192818.1069475-1-tj@kernel.org> <20190726151321.GF2868@twin.jikos.cz> <20190905115937.GA2850@twin.jikos.cz> <20190906174656.GQ2263813@devbig004.ftw2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190906174656.GQ2263813@devbig004.ftw2.facebook.com> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 06, 2019 at 10:46:56AM -0700, Tejun Heo wrote: > On Thu, Sep 05, 2019 at 01:59:37PM +0200, David Sterba wrote: > > On Fri, Jul 26, 2019 at 05:13:21PM +0200, David Sterba wrote: > > > On Wed, Jul 10, 2019 at 12:28:13PM -0700, Tejun Heo wrote: > > > > This patchset contains only the btrfs part of the following patchset. > > > > > > > > [1] [PATCHSET v2 btrfs/for-next] blkcg, btrfs: fix cgroup writeback support > > > > > > > > The block part has already been applied to > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/ for-linus > > > > > > > > with some naming changes. This patchset has been updated accordingly. > > > > > > I'm going to add this patchset to for-next to get some testing coverage, > > > there are some comments pending, but that are changelog updates and > > > refactoring. > > > > No updates, so patchset stays in for-next, closest merge target is 5.5. > > Sorry about dropping the ball. It looked like Chris and Nikolay > weren't agreeing so I wasn't sure what the next step should be and > then forgot about it. The following is the discussion. > > https://lore.kernel.org/linux-btrfs/c2419d01-5c84-3fb4-189e-4db519d08796@suse.com/ > > What do you think about the exchange? I've read the thread again and talked to Nikolay. After going through the questions raised for patch 3/5, I'm more or less ok with merging it as there are no blockers. I'll update the changelogs with points from the discussion. The patchset has been in for-next for some months now so we have testing coverage but we'll have more in the main devel patch queue, that I'll add after I do one more review pass.