[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190131171306.55710d0820deb12282873fab@linux-foundation.org>
Date: Thu, 31 Jan 2019 17:13:06 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Tobin C. Harding" <me@...in.cc>
Cc: "Tobin C. Harding" <tobin@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/slab: Increase width of first /proc/slabinfo column
On Fri, 1 Feb 2019 11:58:38 +1100 "Tobin C. Harding" <me@...in.cc> wrote:
> On Fri, Feb 01, 2019 at 11:42:42AM +1100, Tobin C. Harding wrote:
> [snip]
>
> This applies on top of Linus' tree
>
> commit e74c98ca2d6a ('gfs2: Revert "Fix loop in gfs2_rbm_find"')
>
> For this patch I doubt very much that it matters but for the record I
> can't find mention in MAINTAINERS which tree to base work on for slab
> patches. Are mm patches usually based of an mm tree or do you guys work
> off linux-next?
It's usually best to work off current mainline and I handle the
integration stuff.
Powered by blists - more mailing lists