From: Andrew Jones <drjones@redhat.com>
To: qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-arm] [PATCH 0/5] create the mach-virt 2.7 machine type
Date: Wed, 8 Jun 2016 20:24:46 +0200 [thread overview]
Message-ID: <1465410291-2971-1-git-send-email-drjones@redhat.com> (raw)
This is the first new machine type mach-virt has received
(2.6 being the first versioned machine type), so we need to
do a bit more than the average "new machine type" patch.
The first four patches prepare for easy-adding of machine
types. The last patch adds the 2.7 type.
Andrew Jones (5):
hw/arm/virt: separate versioned type-init code
hw/arm/virt: set is_default
hw/arm/virt: introduce DEFINE_VIRT_MACHINE
hw/arm/virt: introduce DEFINE_VIRT_MACHINE_AS_LATEST
hw/arm/virt: create the 2.7 machine type
hw/arm/virt.c | 66 ++++++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 50 insertions(+), 16 deletions(-)
--
2.4.11
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <drjones@redhat.com>
To: qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, wei@redhat.com
Subject: [Qemu-devel] [PATCH 0/5] create the mach-virt 2.7 machine type
Date: Wed, 8 Jun 2016 20:24:46 +0200 [thread overview]
Message-ID: <1465410291-2971-1-git-send-email-drjones@redhat.com> (raw)
This is the first new machine type mach-virt has received
(2.6 being the first versioned machine type), so we need to
do a bit more than the average "new machine type" patch.
The first four patches prepare for easy-adding of machine
types. The last patch adds the 2.7 type.
Andrew Jones (5):
hw/arm/virt: separate versioned type-init code
hw/arm/virt: set is_default
hw/arm/virt: introduce DEFINE_VIRT_MACHINE
hw/arm/virt: introduce DEFINE_VIRT_MACHINE_AS_LATEST
hw/arm/virt: create the 2.7 machine type
hw/arm/virt.c | 66 ++++++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 50 insertions(+), 16 deletions(-)
--
2.4.11
next reply other threads:[~2016-06-08 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 18:24 Andrew Jones [this message]
2016-06-08 18:24 ` [Qemu-devel] [PATCH 0/5] create the mach-virt 2.7 machine type Andrew Jones
2016-06-08 18:24 ` [Qemu-arm] [PATCH 1/5] hw/arm/virt: separate versioned type-init code Andrew Jones
2016-06-08 18:24 ` [Qemu-devel] " Andrew Jones
2016-06-09 18:27 ` Peter Maydell
2016-06-09 18:27 ` Peter Maydell
2016-06-08 18:24 ` [Qemu-arm] [PATCH 2/5] hw/arm/virt: set is_default Andrew Jones
2016-06-08 18:24 ` [Qemu-devel] " Andrew Jones
2016-06-09 18:27 ` Peter Maydell
2016-06-09 18:27 ` Peter Maydell
2016-06-08 18:24 ` [Qemu-arm] [PATCH 3/5] hw/arm/virt: introduce DEFINE_VIRT_MACHINE Andrew Jones
2016-06-08 18:24 ` [Qemu-devel] " Andrew Jones
2016-06-09 18:29 ` Peter Maydell
2016-06-09 18:29 ` Peter Maydell
2016-06-08 18:24 ` [Qemu-arm] [PATCH 4/5] hw/arm/virt: introduce DEFINE_VIRT_MACHINE_AS_LATEST Andrew Jones
2016-06-08 18:24 ` [Qemu-devel] " Andrew Jones
2016-06-09 18:30 ` [Qemu-arm] " Peter Maydell
2016-06-09 18:30 ` [Qemu-devel] " Peter Maydell
2016-06-08 18:24 ` [Qemu-devel] [PATCH 5/5] hw/arm/virt: create the 2.7 machine type Andrew Jones
2016-06-08 18:24 ` Andrew Jones
2016-06-09 16:06 ` Alex Bennée
2016-06-09 16:19 ` Andrew Jones
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=1465410291-2971-1-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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.