From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Andrew Jones <drjones@redhat.com>, Peter Lieven <pl@kamp.de>
Subject: Re: [Qemu-devel] [PATCH RESEND v2 0/3] vl: smp_parse sanity checks
Date: Thu, 08 Jan 2015 11:48:30 +0100 [thread overview]
Message-ID: <54AE607E.4050709@redhat.com> (raw)
In-Reply-To: <1418957987-28511-1-git-send-email-ehabkost@redhat.com>
On 19/12/2014 03:59, Eduardo Habkost wrote:
> From the original series sent by Andrew, only patch 1/3 was kept. Patch 2/3
> from v1 was replaced by a safer fix. Patch 3/3 was removed because it generates
> a warning even on the most common use-case ("-smp <n>" without any extra
> options).
>
> Andrew Jones (1):
> vl: fix max_cpus check
>
> Eduardo Habkost (2):
> vl: Avoid unnecessary 'if' nesting
> vl: Don't silently change topology when all -smp options were set
>
> vl.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
Eduardo, I forgot the status of these patches. Should I just apply
them? If so, can you take care of documenting the changes in the 2.3
release notes?
Paolo
next prev parent reply other threads:[~2015-01-08 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 2:59 [Qemu-devel] [PATCH RESEND v2 0/3] vl: smp_parse sanity checks Eduardo Habkost
2014-12-19 2:59 ` [Qemu-devel] [PATCH RESEND v2 1/3] vl: Avoid unnecessary 'if' nesting Eduardo Habkost
2014-12-19 2:59 ` [Qemu-devel] [PATCH RESEND v2 2/3] vl: fix max_cpus check Eduardo Habkost
2014-12-19 2:59 ` [Qemu-devel] [PATCH RESEND v2 3/3] vl: Don't silently change topology when all -smp options were set Eduardo Habkost
2015-01-08 10:48 ` Paolo Bonzini [this message]
2015-01-08 13:22 ` [Qemu-devel] [PATCH RESEND v2 0/3] vl: smp_parse sanity checks Eduardo Habkost
2015-01-08 16:36 ` Paolo Bonzini
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=54AE607E.4050709@redhat.com \
--to=pbonzini@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.