From: Andrew Jones <drjones@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, ehabkost@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] hw/arm/virt: max-cpus init/check fixup
Date: Sun, 18 Oct 2015 19:35:26 +0200 [thread overview]
Message-ID: <1445189728-860-1-git-send-email-drjones@redhat.com> (raw)
Changes from v1
. drop the RFC patch "arm_gic_common.h: add gicv2 aliases for defines" [Peter]
. add a patch to cleanup vl.c's max-cpu error message a little [Drew]
. cleanup mach-virt's new error message [Peter]
. make the error message exactly like vl's cleaned up message [Drew]
. add a comment to virt_class_init explaining that we'll further restrict
max_cpus later [Peter]
---
Sorry to be so late getting this simple v2 out. I was trying to
get a new feature (qmp-dump-guest-memory support for arm) posted
before the 2.5 soft freeze (but missed that anyway...)
Andrew Jones (2):
vl: trivial: minor tweaks to a max-cpu error msg
hw/arm/virt: don't use a15memmap directly
hw/arm/virt.c | 25 +++++++++++++++++++++----
vl.c | 4 ++--
2 files changed, 23 insertions(+), 6 deletions(-)
--
2.4.3
next reply other threads:[~2015-10-18 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 17:35 Andrew Jones [this message]
2015-10-18 17:35 ` [Qemu-devel] [PATCH 1/2] vl: trivial: minor tweaks to a max-cpu error msg Andrew Jones
2015-10-19 18:51 ` Eduardo Habkost
2015-10-20 12:05 ` Paolo Bonzini
2015-10-20 7:12 ` Markus Armbruster
2015-10-26 13:00 ` Andrew Jones
2015-10-26 13:38 ` Eduardo Habkost
2015-10-18 17:35 ` [Qemu-devel] [PATCH v2 2/2] hw/arm/virt: don't use a15memmap directly Andrew Jones
2015-10-19 15:24 ` [Qemu-devel] [PATCH v2 0/2] hw/arm/virt: max-cpus init/check fixup Laszlo Ersek
2015-10-23 15:01 ` Peter Maydell
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=1445189728-860-1-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).