From: Avi Kivity <avi@qumranet.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL][RESEND] KVM cpu hotplug fixes
Date: Fri, 01 Jun 2007 19:32:05 +0300 [thread overview]
Message-ID: <46604A05.6060507@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.0.98.0706010819050.3957@woody.linux-foundation.org>
Linus Torvalds wrote:
> Don't send me pull requests like this. And absolutely do NOT send them as
> resends. I just get grumpy.
>
> If all the added code had been KVM-only, I might not care. But when the
> bulk of the code touches core files, you had better explain why this is so
> important that it cannot wait for the next merge window.
Ok. This was really wanted by laptop-carrying users, but I guess
they'll have to wait for 2.6.23.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-06-01 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 6:11 [GIT PULL][RESEND] KVM cpu hotplug fixes Avi Kivity
2007-06-01 15:22 ` Linus Torvalds
2007-06-01 16:32 ` Avi Kivity [this message]
2007-06-02 7:03 ` [kvm-devel] " Jun Koi
2007-06-02 7:32 ` 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=46604A05.6060507@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--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