[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190906174656.GQ2263813@devbig004.ftw2.facebook.com>
Date: Fri, 6 Sep 2019 10:46:56 -0700
From: Tejun Heo <tj@...nel.org>
To: dsterba@...e.cz, josef@...icpanda.com, clm@...com,
dsterba@...e.com, axboe@...nel.dk, jack@...e.cz,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
kernel-team@...com
Subject: Re: [PATCHSET v3 btrfs/for-next] btrfs: fix cgroup writeback support
Hello, David.
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:
> > > Hello,
> > >
> > > 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?
Thanks.
--
tejun
Powered by blists - more mailing lists