linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: linux-next: origin tree build warning
Date: Thu, 11 Jun 2009 11:27:46 +1000	[thread overview]
Message-ID: <20090611112746.802a24cb.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]

Hi all,

Today's linux-next build (x86_64 allmodconfig) produced this warning:

arch/x86/mm/memtest.c: In function 'memtest':
arch/x86/mm/memtest.c:56: warning: comparison of distinct pointer types lacks a cast
arch/x86/mm/memtest.c:58: warning: comparison of distinct pointer types lacks a cast

Introduced by commit c9690998ef48ffefeccb91c70a7739eebdea57f9 ("x86:
memtest: remove 64-bit division").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-06-11  1:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  1:27 Stephen Rothwell [this message]
2009-06-11 10:29 ` [PATCH] x86: memtest: fix compile warning Andreas Herrmann
2009-06-11 14:21   ` Thomas Gleixner
2009-06-11 14:30     ` H. Peter Anvin
2009-06-11 15:26     ` Andreas Herrmann
2009-06-12 13:11       ` Andreas Herrmann
2009-06-11 17:19     ` Yinghai Lu
2009-06-11 21:05       ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  0:09 linux-next: origin tree build warning Stephen Rothwell
2010-01-18  4:05 Stephen Rothwell
2010-01-18  4:14 ` Stephen Rothwell
2010-01-18  4:29   ` Wu, Fengguang
2010-01-18  5:40     ` Stephen Rothwell
2010-01-19  0:12       ` Stephen Rothwell
2010-01-19 21:05         ` Greg KH
2010-01-19 21:11           ` Greg KH
2010-01-19 23:47             ` Stephen Rothwell
     [not found] <20100101112914.41bc5f77.sfr@canb.auug.org.au>
2010-01-01  0:34 ` Linus Torvalds
2010-01-01  1:02   ` Stephen Rothwell
2010-01-01  1:16     ` Rafael J. Wysocki
2009-12-17  0:10 Stephen Rothwell
2009-12-16  3:52 Stephen Rothwell
2009-12-13 23:24 Stephen Rothwell
2009-12-14  7:24 ` Joe Perches
2009-11-29 23:01 Stephen Rothwell
2009-10-30  3:30 Stephen Rothwell
2009-10-11 23:56 Stephen Rothwell
2009-08-25  0:11 Stephen Rothwell
2009-08-25  2:37 ` David Miller
2009-06-23  0:36 Stephen Rothwell
2009-06-22  1:01 [ofa-general] " Stephen Rothwell
2009-06-22  3:11 ` FUJITA Tomonori
2009-06-19  1:13 Stephen Rothwell
2009-06-19  8:45 ` Kristoffer Ericson
2009-06-19  0:27 Stephen Rothwell
2009-06-19  0:28 ` Stephen Rothwell
2009-04-29  4:49 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=20090611112746.802a24cb.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andreas.herrmann3@amd.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=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;
as well as URLs for NNTP newsgroup(s).