All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
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
Subject: Re: linux-next: tip tree build warning
Date: Tue, 04 Aug 2009 12:24:49 -0400	[thread overview]
Message-ID: <1249403089.4634.139.camel@localhost.localdomain> (raw)
In-Reply-To: <20090804161640.70817ee6.sfr@canb.auug.org.au>

On Tue, 2009-08-04 at 16:16 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> 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.

-- Steve

  reply	other threads:[~2009-08-04 16:25 UTC|newest]

Thread overview: 47+ 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 [this message]
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
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 17:09             ` Christopher Li
2009-09-14 18:17             ` Steven Rostedt
2009-09-14 18:17               ` Steven Rostedt
2009-09-14 18:23               ` Peter Zijlstra
2009-09-14 18:23                 ` Peter Zijlstra
2009-09-14 18:31                 ` Steven Rostedt
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-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
  -- strict thread matches above, loose matches on Subject: below --
2009-09-11  8:56 linux-next: tip tree build warning Stephen Rothwell
2009-09-13 20:20 ` Geert Uytterhoeven
2009-10-13  3:42 Stephen Rothwell
2009-10-28  7:14 Stephen Rothwell
2009-10-28  7:31 ` Ingo Molnar
2009-10-28  7:41   ` Stephen Rothwell
2009-10-28  7:48     ` Stephen Rothwell
2009-10-28  7:50       ` Ingo Molnar
2009-11-08 13:16         ` Cyrill Gorcunov
2009-11-08 13:32           ` Ingo Molnar
2009-11-08 13:43             ` Cyrill Gorcunov
2009-11-08 18:42             ` Cyrill Gorcunov
2009-11-08 23:39           ` Stephen Rothwell
2009-11-08 21:30         ` Cyrill Gorcunov
2009-11-09  8:10           ` Ingo Molnar
2009-11-16  5:25 Stephen Rothwell
2009-11-16 17:05 ` Randy Dunlap
2009-11-23 18:05   ` Randy Dunlap
2009-11-25 10:53 Stephen Rothwell
2009-11-25 12:28 ` Frederic Weisbecker
2009-12-11  4:38 Stephen Rothwell
2009-12-30 23:45 Stephen Rothwell
2010-02-01  7:12 Stephen Rothwell
2010-02-01  7:22 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=1249403089.4634.139.camel@localhost.localdomain \
    --to=srostedt@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.