linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Ranganathan Desikan <ravi@jetztechnologies.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	arvino55@gmail.com, bluesmoke-devel@lists.sourceforge.net,
	linux-edac@vger.kernel.org
Subject: Re: linux-next: Tree for April 21 (i82975x_edac)
Date: Thu, 21 Apr 2011 08:51:24 -0700	[thread overview]
Message-ID: <20110421085124.4a44d048.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110421132045.5af1b953.sfr@canb.auug.org.au>

On Thu, 21 Apr 2011 13:20:45 +1000 Stephen Rothwell wrote:

> Changes since 20110420:


on i386:

drivers/edac/i82975x_edac.c:298: warning: integer constant is too large for 'unsigned long' type

which is:

	if (info->xeap & 1)
		page |= 0x100000000ul; <<<<<<<<<<<<<<<

but page is unsigned long (32 bits), while 0x100000000ul is more than 32 bits,
so that line isn't setting a bit in <page>.  Is it a bug, or this driver isn't
applicable to X86_32, or what?


thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-04-21 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  3:20 linux-next: Tree for April 21 Stephen Rothwell
2011-04-21 14:41 ` linux-next: Tree for April 21 (md/raid456) Randy Dunlap
2011-04-21 15:51 ` Randy Dunlap [this message]
2011-04-23  8:21   ` linux-next: Tree for April 21 (i82975x_edac) Arvind R
2011-04-23 15:45     ` Randy Dunlap
2011-04-24  6:29       ` Arvind R
2011-04-25  2:13         ` Randy Dunlap
2011-04-25  5:51           ` Arvind R
2011-04-25  7:00           ` Jason Uhlenkott
2011-04-21 16:09 ` [PATCH -next] kvm: fix const value warning on i386 Randy Dunlap
2011-04-24  7:12   ` Avi Kivity

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=20110421085124.4a44d048.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=arvino55@gmail.com \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ravi@jetztechnologies.com \
    --cc=sfr@canb.auug.org.au \
    /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).