From: Alexander Graf <agraf@suse.de>
To: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: aik@au1.ibm.com, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] ppc/spapr: Fix MAX_CPUS to 255
Date: Mon, 28 Jul 2014 15:41:26 +0200 [thread overview]
Message-ID: <53D65306.9020905@suse.de> (raw)
In-Reply-To: <1403851658-13128-3-git-send-email-nikunj@linux.vnet.ibm.com>
On 27.06.14 08:47, Nikunj A Dadhania wrote:
> MAX_CPUS 256 is inconsistent with qemu supporting upto 255 cpus. This
> MAX_CPUS number was percolated back to "virsh capabilities" with wrong
> max_cpus.
>
> Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Nice one :). Thanks, applied to ppc-next-2.2.
Alex
prev parent reply other threads:[~2014-07-28 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 6:47 [Qemu-devel] [PATCH 3/3] ppc/spapr: Fix MAX_CPUS to 255 Nikunj A Dadhania
2014-07-11 4:28 ` Nikunj A Dadhania
2014-07-28 13:41 ` Alexander Graf [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=53D65306.9020905@suse.de \
--to=agraf@suse.de \
--cc=aik@au1.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).