From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: still FTRACE_SYSCALL_MAX compile error on linux-next? Date: Wed, 2 Sep 2009 15:34:19 +0200 Message-ID: <20090902133419.GA20497@elte.hu> References: <20090902091258.GA4754@osiris.boeblingen.de.ibm.com> <20090902110231.GA3910@elte.hu> <20090902111234.GB4754@osiris.boeblingen.de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:44722 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751716AbZIBNeV (ORCPT ); Wed, 2 Sep 2009 09:34:21 -0400 Content-Disposition: inline In-Reply-To: <20090902111234.GB4754@osiris.boeblingen.de.ibm.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Heiko Carstens Cc: Jason Baron , Frederic Weisbecker , linux-next@vger.kernel.org, Martin Schwidefsky * Heiko Carstens wrote: > On Wed, Sep 02, 2009 at 01:02:31PM +0200, Ingo Molnar wrote: > > > > * Heiko Carstens 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. > > Ok, thanks! pushed it - let me know if there's still trouble in tomorrow's linux-next kernel. Ingo