From: Steven Rostedt <rostedt@goodmis•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: linux-next: build warnings after merge of the final tree
Date: Wed, 14 Dec 2011 11:32:02 -0500 [thread overview]
Message-ID: <1323880322.23971.33.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111214181545.6e13bc954cb7ddce9086e861@canb.auug.org.au>
On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
> Maybe caused by commit d5e553d6e0a4 ("trace: Include <asm/asm-offsets.h>
> 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?
-- Steve
next prev parent reply other threads:[~2011-12-14 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 7:15 linux-next: build warnings after merge of the final tree Stephen Rothwell
2011-12-14 16:32 ` Steven Rostedt [this message]
2011-12-14 16:47 ` H. Peter Anvin
2011-12-22 5:33 ` Stephen Rothwell
2012-01-04 8:06 ` Stephen Rothwell
2012-01-04 9:23 ` hpanvin@gmail•com
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 4:10 Stephen Rothwell
2010-08-02 8:03 ` Benjamin Herrenschmidt
2010-08-02 8:51 ` Stephen Rothwell
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=1323880322.23971.33.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@elte$(echo .)hu \
--cc=paulus@samba$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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