kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH v2] kvm: Add documentation for KVM_CAP_NR_VCPUS
Date: Wed, 11 May 2011 12:58:25 +0300	[thread overview]
Message-ID: <4DCA5DC1.8050208@redhat.com> (raw)
In-Reply-To: <1304970534-7824-1-git-send-email-penberg@kernel.org>

On 05/09/2011 10:48 PM, Pekka Enberg wrote:
> Document KVM_CAP_NR_VCPUS that can be used by the userspace to determine
> maximum number of VCPUs it can create with the KVM_CREATE_VCPU ioctl.

Applied, thanks.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-05-11 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:48 [PATCH v2] kvm: Add documentation for KVM_CAP_NR_VCPUS Pekka Enberg
2011-05-11  9:58 ` 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=4DCA5DC1.8050208@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).