From: "Tobin C. Harding" <me@tobin.cc>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slab: Increase width of first /proc/slabinfo column
Date: Fri, 1 Feb 2019 13:56:30 +1100 [thread overview]
Message-ID: <20190201025630.GA29854@eros.localdomain> (raw)
In-Reply-To: <20190131171306.55710d0820deb12282873fab@linux-foundation.org>
On Thu, Jan 31, 2019 at 05:13:06PM -0800, Andrew Morton wrote:
> On Fri, 1 Feb 2019 11:58:38 +1100 "Tobin C. Harding" <me@tobin.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.
Awesome, thanks.
Tobin
next prev parent reply other threads:[~2019-02-01 2:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 0:42 Tobin C. Harding
2019-02-01 0:58 ` Tobin C. Harding
2019-02-01 1:13 ` Andrew Morton
2019-02-01 2:56 ` Tobin C. Harding [this message]
2019-02-01 2:34 ` Christopher Lameter
2019-02-02 6:47 ` Pekka Enberg
2019-02-01 2:43 ` Matthew Wilcox
2019-02-01 2:58 ` Tobin C. Harding
2019-02-01 22:03 ` Andrew Morton
2019-02-04 5:55 ` Tobin C. Harding
2019-02-04 1:35 ` Tobin C. Harding
2019-02-02 3:27 ` Joe Perches
2019-02-03 23:34 ` Tobin C. Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190201025630.GA29854@eros.localdomain \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tobin@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox