From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Jason Baron <jbaron@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-next@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: still FTRACE_SYSCALL_MAX compile error on linux-next?
Date: Wed, 2 Sep 2009 13:02:31 +0200 [thread overview]
Message-ID: <20090902110231.GA3910@elte.hu> (raw)
In-Reply-To: <20090902091258.GA4754@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> Hi Ingo,
>
> in linux-next I still see this compile error on s390:
>
> kernel/trace/trace_syscalls.c:13: error: 'FTRACE_SYSCALL_MAX' undeclared here (not in a function)
> make[2]: *** [kernel/trace/trace_syscalls.o] Error 1
>
> The fix for this in your tracing/core branch:
> "tracing: Convert event tracing code to use NR_syscalls"
>
> is that branch not part of linux-next?
it is, but it had open bugs so i couldnt push it for some while.
Will push later today most likely.
Ingo
next prev parent reply other threads:[~2009-09-02 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 9:12 still FTRACE_SYSCALL_MAX compile error on linux-next? Heiko Carstens
2009-09-02 11:02 ` Ingo Molnar [this message]
2009-09-02 11:12 ` Heiko Carstens
2009-09-02 13:34 ` 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=20090902110231.GA3910@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jbaron@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.