From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
KVM mailing list <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Build problem strikes again
Date: Mon, 18 Jan 2010 18:59:50 +0100 [thread overview]
Message-ID: <4B54A196.6000507@siemens.com> (raw)
In-Reply-To: <20100118173733.GC22111@redhat.com>
Gleb Natapov wrote:
> On Mon, Jan 18, 2010 at 03:24:45PM -0200, Lucas Meneghel Rodrigues wrote:
>> Today's git tests failed due to kvm-kmod problems again, please verify:
>>
> kvm-kmod needs to copy arch/x86/include/asm/hyperv.h during sync now.
>
Yep, already noticed this in my nightly buildbot run. Will fix soon.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-01-18 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 17:24 Build problem strikes again Lucas Meneghel Rodrigues
2010-01-18 17:37 ` Gleb Natapov
2010-01-18 17:59 ` Jan Kiszka [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=4B54A196.6000507@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mtosatti@redhat.com \
/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