From: Avi Kivity <avi@qumranet.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm-devel <kvm@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] KVM fixes for 2.6.26-rc7
Date: Wed, 25 Jun 2008 10:08:09 +0300 [thread overview]
Message-ID: <4861EED9.2080503@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806241809530.17712@woody.linux-foundation.org>
Linus Torvalds wrote:
> On Wed, 25 Jun 2008, Avi Kivity wrote:
>
>> Linus, please pull from the repo and branch at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git kvm-updates-2.6.26
>>
>> to receive kvm updates for 2.6.26-rc7. The patches fix host oopses,
>> guest interrupt loss, and total kvm clock borkage.
>>
>
> Avi, you _really_ need to start respecting the merge window.
>
> If you can't learn, I will have to just stop pulling from you. This is
> simply too big for this late in the game.
>
> I pulled, but I'm simply not going to continue doing this dance. I don't
> care much for virtualization, so I've let it slide, but you need to learn
> that
>
>
>> 18 files changed, 358 insertions(+), 266 deletions(-)
>>
>
> is simply not acceptable this late.
>
You're right, I guess I should have disabled kvm clock for 2.6.26 (which
makes up the bulk of the changes) and re-enabled it for 2.6.27, but
ended up not resisting the temptation.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-06-25 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 21:05 [GIT PULL] KVM fixes for 2.6.26-rc7 Avi Kivity
2008-06-25 1:12 ` Linus Torvalds
2008-06-25 7:08 ` Avi Kivity [this message]
2008-06-25 16:13 ` Bernd Schubert
2008-06-27 5:18 ` Jeremy Fitzhardinge
2008-06-28 4:02 ` 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=4861EED9.2080503@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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