From: "hpanvin@gmail.com" <hpa@zytor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
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, 04 Jan 2012 01:23:11 -0800 [thread overview]
Message-ID: <f5643ab8-9ba0-4ee6-b61e-403f03525a46@email.android.com> (raw)
In-Reply-To: <20120104190613.2e76daaa000ccf61121fdcc1@canb.auug.org.au>
I thought it had been...? Need to investigate (as baby permits...)
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>Hi again,
>
>On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell
><sfr@canb.auug.org.au> wrote:
>>
>> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" <hpa@zytor.com>
>wrote:
>> >
>> > 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
><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?
>> >
>> > Yes (on both accounts). It was part of the syscall changes; I'll
>move
>> > the include.
>>
>> Ping?
>
>Can we please have this fixed ...
>--
>Cheers,
>Stephen Rothwell sfr@canb.auug.org.au
>http://www.canb.auug.org.au/~sfr/
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2012-01-04 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 7:15 Stephen Rothwell
2011-12-14 16:32 ` Steven Rostedt
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 [this message]
2012-01-08 4:40 ` [tip:x86/syscall] x86: Move <asm/asm-offsets.h> from trace_syscalls.c to asm/syscall.h tip-bot for H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 4:10 linux-next: build warnings after merge of the final tree 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=f5643ab8-9ba0-4ee6-b61e-403f03525a46@email.android.com \
--to=hpa@zytor.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®