From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <srostedt@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning)
Date: Sat, 12 Sep 2009 09:39:06 +0200 [thread overview]
Message-ID: <20090912073906.GA3972@elte.hu> (raw)
In-Reply-To: <20090912165300.9d257283.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Steve,
>
> On Tue, 04 Aug 2009 12:24:49 -0400 Steven Rostedt <srostedt@redhat.com> wrote:
> >
> > On Tue, 2009-08-04 at 16:16 +1000, Stephen Rothwell wrote:
> > >
> > > Today's linux-next build (powerpc ppc64_defconfig) produced these warnings:
> > >
> > > kernel/trace/ring_buffer.c: In function 'rb_head_page_set':
> > > kernel/trace/ring_buffer.c:704: warning: initialization makes pointer from integer without a cast
> > > kernel/trace/ring_buffer.c:704: warning: initialization makes pointer from integer without a cast
> > > kernel/trace/ring_buffer.c: In function 'rb_head_page_replace':
> > > kernel/trace/ring_buffer.c:797: warning: initialization makes integer from pointer without a cast
> > >
> > > Introduced by commit 77ae365eca895061c8bf2b2e3ae1d9ea62869739
> > > ("ring-buffer: make lockless").
> >
> > Thanks, I'll take a look at it.
>
> Now that this is in Linus' tree, can we have a fix for the waning,
> please?
The first warning got fixed 1.5 months ago - the second one at line
797 is still there but harmless - you can ignore it for now, it will
be fixed.
Ingo
next prev parent reply other threads:[~2009-09-12 7:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 6:16 linux-next: tip tree build warning Stephen Rothwell
2009-08-04 16:24 ` Steven Rostedt
2009-09-12 6:53 ` Warning from ring buffer code (Was: Re: linux-next: tip tree build warning) Stephen Rothwell
2009-09-12 7:39 ` Ingo Molnar [this message]
2009-09-12 10:46 ` Stephen Rothwell
2009-09-12 11:12 ` Jaswinder Singh Rajput
2009-09-14 15:16 ` Steven Rostedt
2009-09-14 17:09 ` Christopher Li
2009-09-14 18:17 ` Steven Rostedt
2009-09-14 18:23 ` Peter Zijlstra
2009-09-14 18:31 ` Steven Rostedt
2009-09-14 18:41 ` Frederic Weisbecker
2009-09-15 7:16 ` Peter Zijlstra
2009-09-15 9:01 ` Frédéric Weisbecker
2009-09-14 18:38 ` Frederic Weisbecker
2009-09-14 13:50 ` Steven Rostedt
2009-09-14 13:53 ` Ingo Molnar
2009-09-14 22:36 ` 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=20090912073906.GA3972@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=srostedt@redhat.com \
--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