From: Fengguang Wu <lkp@intel.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: rientjes@google.com, linux-mm@kvack.org,
akpm@linux-foundation.org, kbuild-all@01.org,
linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [kbuild-all] [patch -mm] mm, vmalloc: remove VM_VPAGES
Date: Thu, 19 Nov 2015 20:35:46 +0800 [thread overview]
Message-ID: <20151119123546.GA25179@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <201511192123.DHI75684.FFHOOQSVMLOFJt@I-love.SAKURA.ne.jp>
On Thu, Nov 19, 2015 at 09:23:41PM +0900, Tetsuo Handa wrote:
> Fengguang Wu wrote:
> > Hi David,
> >
> > On Wed, Nov 18, 2015 at 05:00:07PM -0800, David Rientjes wrote:
> > > On Thu, 19 Nov 2015, kbuild test robot wrote:
> > >
> > > > Hi David,
> > > >
> > > > [auto build test ERROR on: next-20151118]
> > > > [also build test ERROR on: v4.4-rc1]
> > > >
> > >
> > > You need to teach your bot what patches I'm proposing for the -mm tree
> > > (notice the patch title) instead of your various trees.
> >
> > Per my understanding linux-next is the -mm tree.
> > Or do you mean some standalone -mm git tree?
> >
> > Thanks,
> > Fengguang
> >
>
> This build error will be gone when
> "[PATCH] tree wide: Use kvfree() than conditional kfree()/vfree()"
> (currently in -mm tree) is applied.
Got it. I can find that patch in the mmotm tree:
git://git.cmpxchg.org/linux-mmotm.git
I'll teach the robot to use it instead of linux-next for [-mm] patches.
Thanks,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-11-19 12:35 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 [this message]
2015-11-19 18:37 ` Johannes Weiner
2015-11-20 1:46 ` Fengguang Wu
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=20151119123546.GA25179@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