On Sun 07-04-13 16:44:07, Li Zefan wrote: > Hi, > > I'm rebasing this patchset against latest linux-next, and it conflicts with > "[PATCH v2] memcg: debugging facility to access dangling memcgs." slightly. > > That is a debugging patch and will never be pushed into mainline, so should I > still base this patchset on that debugging patch? Could you split CONFIG_MEMCG_DEBUG_ASYNC_DESTROY changes into a separate patch so that Andrew could put it on top of the mentioned patch? > Also that patch needs update (and can be simplified) after this patchset: > - move memcg_dangling_add() to mem_cgroup_css_offline() > - remove memcg->memcg_name, and use cgroup_path() in mem_cgroup_dangling_read()? Every improvement is welcome. Thanks -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
