public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kvm@vger.kernel.org
Subject: [PATCH -next] kvm: fix const value warning on i386
Date: Thu, 21 Apr 2011 09:09:22 -0700	[thread overview]
Message-ID: <20110421090922.4d9a275b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110421132045.5af1b953.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

arch/x86/kvm/emulate.c:2598: warning: integer constant is too large for 'long' type

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 arch/x86/kvm/emulate.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20110421.orig/arch/x86/kvm/emulate.c
+++ linux-next-20110421/arch/x86/kvm/emulate.c
@@ -2595,7 +2595,7 @@ static int check_svme_pa(struct x86_emul
 	u64 rax = kvm_register_read(ctxt->vcpu, VCPU_REGS_RAX);
 
 	/* Valid physical address? */
-	if (rax & 0xffff000000000000)
+	if (rax & 0xffff000000000000ULL)
 		return emulate_gp(ctxt, 0);
 
 	return check_svme(ctxt);

  parent reply	other threads:[~2011-04-21 16:09 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 ` linux-next: Tree for April 21 (i82975x_edac) Randy Dunlap
2011-04-23  8:21   ` 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 ` Randy Dunlap [this message]
2011-04-24  7:12   ` [PATCH -next] kvm: fix const value warning on i386 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=20110421090922.4d9a275b.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mtosatti@redhat.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