[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200915131712.GA50425@dschatzberg-fedora-PC0Y6AEN.dhcp.thefacebook.com>
Date: Tue, 15 Sep 2020 09:17:12 -0400
From: Dan Schatzberg <schatzberg.dan@...il.com>
To: Jens Axboe <axboe@...nel.dk>, Tejun Heo <tj@...nel.org>,
Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>,
Shakeel Butt <shakeelb@...gle.com>,
Roman Gushchin <guro@...com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Chris Down <chris@...isdown.name>,
Yang Shi <yang.shi@...ux.alibaba.com>,
Jakub Kicinski <kuba@...nel.org>,
"open list:BLOCK LAYER" <linux-block@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:CONTROL GROUP (CGROUP)" <cgroups@...r.kernel.org>,
"open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
<linux-mm@...ck.org>
Subject: Re: [PATCH v8 0/3] Charge loop device i/o to issuing cgroup
Jens,
How would you like to resolve this patch series? Roman's patch that
this is based off of just made it into linux-next:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/+/928776957ea4e1c35b1c4c35b8fe7203354fbae3
I suppose you can pull that into the block tree and have git merge
resolve it when it all goes to linus. Another option would be routing
this through Andrew's -mm tree (which already has that commit). Up to
you which you prefer.
Powered by blists - more mailing lists