[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220423153321.cts6qhlybkghoe2o@dev0025.ash9.facebook.com>
Date: Sat, 23 Apr 2022 08:33:21 -0700
From: David Vernet <void@...ifault.com>
To: Roman Gushchin <roman.gushchin@...ux.dev>
Cc: akpm@...ux-foundation.org, tj@...nel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
cgroups@...r.kernel.org, hannes@...xchg.org, mhocko@...nel.org,
shakeelb@...gle.com, kernel-team@...com
Subject: Re: [PATCH 1/5] cgroups: Refactor children cgroups in memcg tests
On Sat, Apr 23, 2022 at 08:19:12AM -0700, Roman Gushchin wrote:
>
> > On Apr 23, 2022, at 4:30 AM, David Vernet <void@...ifault.com> wrote:
> >
> > On Fri, Apr 22, 2022 at 04:04:15PM -0700, Roman Gushchin wrote:
> >>
> >
> > Thanks for the reviews on this patchset, Roman. FYI I think Andrew already
> > merged these patches to the -mm tree. I'll send out a follow-on patch that
> > fixes everything you pointed out, both here and on the other patches in the
> > set.
>
> The mm tree isn’t a git tree, but a collection of the text patches, managed by Andrew. So you can send a new version and Andrew can update it in place. It’s happening all the time: mostly for adding reviewed-by/acked-by tags etc, but for code updates as well.
> It’s not uncommon for some patchset to mature while being in the mm tree, this allows to include them into linux-next and give some more testing, but without doing many reverts/fixups (Andrew is often squashing fixups into the original patch too). So long story short, you can just send a new version, especially because all changes all minor.
Ah, that makes sense. Thanks for explaining that. I'll send out a v2 of the
patches shortly, then!
Powered by blists - more mailing lists