From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 203/499] include/linux/vmstat.h:32:2: error: implicit declaration of function 'raw_cpu_inc'
Date: Fri, 21 Mar 2014 19:12:16 -0700 [thread overview]
Message-ID: <20140321191216.776e3281.akpm@linux-foundation.org> (raw)
In-Reply-To: <532cde58.CgQv/f5/Xxy3YpRB%fengguang.wu@intel.com>
On Sat, 22 Mar 2014 08:50:32 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: 4ddd4bc6e081ef29f7adaacb357b77052fefcd7e
> commit: 4ac4f1a27eed39f833aa8874515127e3bd0ff971 [203/499] vmstat: use raw_cpu_ops to avoid false positives on preemption checks
> config: make ARCH=x86_64 allnoconfig
>
> Note: the mmotm/master HEAD 4ddd4bc6e081ef29f7adaacb357b77052fefcd7e builds fine.
> It only hurts bisectibility.
>
> All error/warnings:
>
> In file included from include/linux/mm.h:897:0,
> from include/linux/suspend.h:8,
> from arch/x86/kernel/asm-offsets.c:12:
> include/linux/vmstat.h: In function '__count_vm_event':
> >> include/linux/vmstat.h:32:2: error: implicit declaration of function 'raw_cpu_inc' [-Werror=implicit-function-declaration]
> raw_cpu_inc(vm_event_states.event[item]);
> ^
> include/linux/vmstat.h: In function '__count_vm_events':
> >> include/linux/vmstat.h:42:2: error: implicit declaration of function 'raw_cpu_add' [-Werror=implicit-function-declaration]
> raw_cpu_add(vm_event_states.event[item], delta);
> ^
> cc1: some warnings being treated as errors
> make[2]: *** [arch/x86/kernel/asm-offsets.s] Error 1
> make[2]: Target `__build' not remade because of errors.
> make[1]: *** [prepare0] Error 2
> make[1]: Target `prepare' not remade because of errors.
> make: *** [sub-make] Error 2
bah, OK, patch ordering problem. I'll shuffle them around and we'll be
stuck with a small and quite minor bisection window where the kernel
emits warnings at runtime.
--
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-03-22 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 0:50 kbuild test robot
2014-03-22 2:12 ` Andrew Morton [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=20140321191216.776e3281.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--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