From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Marcelo Tosatti <mtosatti@redhat.com>,
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 19:15:34 +0200 [thread overview]
Message-ID: <4B573A36.9090308@redhat.com> (raw)
In-Reply-To: <20100120091241.3f10428d.randy.dunlap@oracle.com>
On 01/20/2010 07:12 PM, Randy Dunlap wrote:
> 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
>
>
Gleb already posted a patch to fix this.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-20 17:15 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 ` linux-next: Tree for January 20 (kvm warnings) Randy Dunlap
2010-01-20 17:15 ` Avi Kivity [this message]
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=4B573A36.9090308@redhat.com \
--to=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=randy.dunlap@oracle.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 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.