From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmemtrace: fix build breakage in befs
Date: Tue, 24 Mar 2009 11:34:17 +0100 [thread overview]
Message-ID: <20090324103417.GA30579@elte.hu> (raw)
In-Reply-To: <20090324101232.GA26228@elte.hu>
64-bit defconfig:
In file included from include/linux/slub_def.h:14,
from include/linux/slab.h:154,
from include/linux/percpu.h:6,
from include/linux/rcutree.h:37,
from include/linux/rcupdate.h:61,
from include/linux/tracepoint.h:19,
from include/linux/module.h:20,
from include/linux/crypto.h:22,
from arch/x86/kernel/asm-offsets_64.c:8,
from arch/x86/kernel/asm-offsets.c:5:
include/trace/kmemtrace.h:24: error: expected ‘)’ before ‘(’ token
include/trace/kmemtrace.h:31: error: expected ‘)’ before ‘(’ token
include/trace/kmemtrace.h:38: error: expected ‘)’ before ‘(’ token
include/trace/kmemtrace.h:46: error: expected ‘)’ before ‘(’ token
include/trace/kmemtrace.h:54: error: expected ‘)’ before ‘(’ token
include/trace/kmemtrace.h:57: error: expected ‘)’ before ‘(’ token
In file included from include/linux/slab.h:154,
from include/linux/percpu.h:6,
from include/linux/rcutree.h:37,
from include/linux/rcupdate.h:61,
from include/linux/tracepoint.h:19,
from include/linux/module.h:20,
from include/linux/crypto.h:22,
from arch/x86/kernel/asm-offsets_64.c:8,
from arch/x86/kernel/asm-offsets.c:5:
include/linux/slub_def.h: In function ‘kmalloc_large’:
include/linux/slub_def.h:236: error: implicit declaration of function ‘trace_kmalloc’
include/linux/slub_def.h: In function ‘kmalloc_node’:
include/linux/slub_def.h:296: error: implicit declaration of function ‘trace_kmalloc_node’
3.65user 0.62system 0:02.86elapsed 149%CPU (0avgtext+0avgdata 0maxresident)k
next prev parent reply other threads:[~2009-03-24 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 8:43 [PATCH] kmemtrace: fix build breakage in befs Pekka Enberg
2009-03-24 8:51 ` Ingo Molnar
2009-03-24 8:54 ` Pekka Enberg
2009-03-24 8:56 ` Ingo Molnar
2009-03-24 8:57 ` Pekka Enberg
2009-03-24 9:07 ` Ingo Molnar
2009-03-24 9:15 ` Pekka Enberg
2009-03-24 9:17 ` Ingo Molnar
2009-03-24 9:22 ` Pekka Enberg
2009-03-24 9:31 ` Ingo Molnar
2009-03-24 9:34 ` Ingo Molnar
2009-03-24 9:46 ` Ingo Molnar
2009-03-24 10:12 ` Ingo Molnar
2009-03-24 10:34 ` Ingo Molnar [this message]
2009-03-24 9:38 ` Pekka Enberg
2009-03-24 9:53 ` Ingo Molnar
2009-03-24 13:09 ` Alexey Dobriyan
2009-03-24 13:11 ` Pekka Enberg
2009-03-24 16:32 ` Eduard - Gabriel Munteanu
2009-03-24 21:02 ` Ingo Molnar
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=20090324103417.GA30579@elte.hu \
--to=mingo@elte.hu \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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