From: Fengguang Wu <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 108/319] kernel/events/uprobes.c:319:2: error: implicit declaration of function 'mem_cgroup_charge_anon'
Date: Fri, 21 Nov 2014 16:36:04 -0800 [thread overview]
Message-ID: <20141122003604.GA24535@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20140626130223.2db7a085421f594eb1707eb8@linux-foundation.org>
Hi Andrew,
On Thu, Jun 26, 2014 at 01:02:23PM -0700, Andrew Morton wrote:
> On Thu, 26 Jun 2014 09:05:08 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
>
> > tree: git://git.cmpxchg.org/linux-mmotm.git master
> > head: 9477ec75947f2cf0fc47e8ab781a5e9171099be2
> > commit: 5c83b35612a2f2894b54d902ac50612cec2e1926 [108/319] mm: memcontrol: rewrite charge API
> > config: i386-randconfig-ha2-0626 (attached as .config)
> >
> > Note: the mmotm/master HEAD 9477ec75947f2cf0fc47e8ab781a5e9171099be2 builds fine.
> > It only hurts bisectibility.
> >
> > All error/warnings:
> >
> > kernel/events/uprobes.c: In function 'uprobe_write_opcode':
> > >> kernel/events/uprobes.c:319:2: error: implicit declaration of function 'mem_cgroup_charge_anon' [-Werror=implicit-function-declaration]
> > if (mem_cgroup_charge_anon(new_page, mm, GFP_KERNEL))
> > ^
> > cc1: some warnings being treated as errors
>
> The next patch mm-memcontrol-rewrite-charge-api-fix-3.patch fixes this
> up. Is there something I did which fooled the buildbot's
> hey-theres-a-fixup-patch detector?
Git log shows that the next patch is "kernel: uprobes: switch to new
memcg charge protocol" and in fact there is no
mm-memcontrol-rewrite-charge-api-fix-3.patch at the time this git
branch is created:
34346b2c memcg: mem_cgroup_charge_statistics needs preempt_disable
fix 2 => ac43603 mm: memcontrol: rewrite uncharge API fix 2
fix 1 => 0d971aa mm: memcontrol: rewrite uncharge API
a9f32f2 kernel: uprobes: switch to new memcg charge protocol
first bad commit => 5c83b35 mm: memcontrol: rewrite charge API
That should explain why the buildbot reported the error out.
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>
prev parent reply other threads:[~2014-11-22 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 1:05 kbuild test robot
2014-06-26 20:02 ` Andrew Morton
2014-11-22 0:36 ` Fengguang Wu [this message]
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=20141122003604.GA24535@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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