From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: linux-next: build warnings after merge of the final tree Date: Wed, 14 Dec 2011 08:47:01 -0800 Message-ID: <4EE8D305.8020407@zytor.com> References: <20111214181545.6e13bc954cb7ddce9086e861@canb.auug.org.au> <1323880322.23971.33.camel@gandalf.stny.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:59840 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756194Ab1LNQrn (ORCPT ); Wed, 14 Dec 2011 11:47:43 -0500 In-Reply-To: <1323880322.23971.33.camel@gandalf.stny.rr.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Steven Rostedt Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org On 12/14/2011 08:32 AM, Steven Rostedt wrote: > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > >> Maybe caused by commit d5e553d6e0a4 ("trace: Include >> in trace_syscalls.c") from the tip tree. These warnings may have been >> here for a while as it is hard to catch the new ones among the flood. >> > > hpa, > > Was this change only needed for x86? If so, could you put that into > asm/ftrace.h instead? > Yes (on both accounts). It was part of the syscall changes; I'll move the include. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.zytor.com (terminus.zytor.com [IPv6:2001:1868:205::10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id AC15B1007D6 for ; Thu, 15 Dec 2011 03:47:41 +1100 (EST) Message-ID: <4EE8D305.8020407@zytor.com> Date: Wed, 14 Dec 2011 08:47:01 -0800 From: "H. Peter Anvin" MIME-Version: 1.0 To: Steven Rostedt Subject: Re: linux-next: build warnings after merge of the final tree References: <20111214181545.6e13bc954cb7ddce9086e861@canb.auug.org.au> <1323880322.23971.33.camel@gandalf.stny.rr.com> In-Reply-To: <1323880322.23971.33.camel@gandalf.stny.rr.com> Content-Type: text/plain; charset=UTF-8 Cc: Stephen Rothwell , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, Paul Mackerras , Thomas Gleixner , linuxppc-dev@lists.ozlabs.org, Ingo Molnar List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 12/14/2011 08:32 AM, Steven Rostedt wrote: > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote: > >> Maybe caused by commit d5e553d6e0a4 ("trace: Include >> in trace_syscalls.c") from the tip tree. These warnings may have been >> here for a while as it is hard to catch the new ones among the flood. >> > > hpa, > > Was this change only needed for x86? If so, could you put that into > asm/ftrace.h instead? > Yes (on both accounts). It was part of the syscall changes; I'll move the include. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.