From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] qemu-options: Rewrite -numa documentation
Date: Mon, 23 Jan 2017 16:06:30 -0200 [thread overview]
Message-ID: <20170123180632.28942-1-ehabkost@redhat.com> (raw)
The first patch is a trivial fix to an issue reported by Peter
Maydell. The second patch rewrites all the rest.
Eduardo Habkost (2):
qemu-options: Rename variables on the -numa "cpus" option
qemu-options: Rewrite -numa documentation
qemu-options.hx | 46 ++++++++++++++++++++++++++++++++--------------
1 file changed, 32 insertions(+), 14 deletions(-)
--
2.11.0.259.g40922b1
next reply other threads:[~2017-01-23 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 18:06 Eduardo Habkost [this message]
2017-01-23 18:06 ` [Qemu-devel] [PATCH 1/2] qemu-options: Rename variables on the -numa "cpus" option Eduardo Habkost
2017-01-23 18:36 ` Peter Maydell
2017-01-23 18:06 ` [Qemu-devel] [PATCH 2/2] qemu-options: Rewrite -numa documentation Eduardo Habkost
2017-01-24 10:14 ` Igor Mammedov
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=20170123180632.28942-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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).