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-4db519d08...@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.

Reply via email to