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: Re: linux-next: Tree for January 20 (kvm warnings)
Date: Wed, 20 Jan 2010 09:12:41 -0800 [thread overview]
Message-ID: <20100120091241.3f10428d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100120181016.6ba3e504.sfr@canb.auug.org.au>
On Wed, 20 Jan 2010 18:10:16 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100119:
>
> The kvm tree lost its build failure.
on i386/X86_32:
arch/x86/kvm/x86.c:3810: warning: left shift count >= width of type
arch/x86/kvm/x86.c:3812: warning: left shift count >= width of type
arch/x86/kvm/x86.c:3814: warning: left shift count >= width of type
---
~Randy
next prev parent reply other threads:[~2010-01-20 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 7:10 linux-next: Tree for January 20 Stephen Rothwell
2010-01-20 17:12 ` Randy Dunlap [this message]
2010-01-20 17:15 ` linux-next: Tree for January 20 (kvm warnings) 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=20100120091241.3f10428d.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;
as well as URLs for NNTP newsgroup(s).