mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fengguang Wu <lkp@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kbuild-all@01.org, rientjes@google.com,
	akpm@linux-foundation.org
Subject: Re: [kbuild-all] [patch -mm] mm, vmalloc: remove VM_VPAGES
Date: Fri, 20 Nov 2015 09:46:21 +0800	[thread overview]
Message-ID: <20151120014621.GA28477@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20151119183745.GA2555@cmpxchg.org>

On Thu, Nov 19, 2015 at 01:37:45PM -0500, Johannes Weiner wrote:
> Hi Fengguang,
> 
> On Thu, Nov 19, 2015 at 08:35:46PM +0800, Fengguang Wu wrote:
> > 
> >         git://git.cmpxchg.org/linux-mmotm.git
> > 
> > I'll teach the robot to use it instead of linux-next for [-mm] patches.
> 
> Yup, that seems like a more suitable base.
> 
> But you might even consider putting them on top of linux-mmots.git,

Yes, sure. I'll apply [-mm] LKML patches onto linux-mmots.git.

Thanks,
Fengguang

> which is released more frequently than mmotm. Not sure what other MM
> hackers do, but I tend to develop against mmots, and there could be
> occasional breakage when dependencies haven't yet trickled into mmotm.
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all

  reply	other threads:[~2015-11-20  1:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  0:30 David Rientjes
2015-11-19  0:39 ` kbuild test robot
2015-11-19  1:00   ` David Rientjes
2015-11-19 11:33     ` [kbuild-all] " Fengguang Wu
2015-11-19 12:23       ` Tetsuo Handa
2015-11-19 12:35         ` Fengguang Wu
2015-11-19 18:37           ` Johannes Weiner
2015-11-20  1:46             ` Fengguang Wu [this message]
2015-11-19  0:40 ` kbuild test robot

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=20151120014621.GA28477@wfg-t540p.sh.intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rientjes@google.com \
    /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
all inboxes | Powered by JetHome®