From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] Remove wrong savevm sections
Date: Thu, 24 Feb 2011 15:17:13 +0100 [thread overview]
Message-ID: <cover.1298556891.git.quintela@redhat.com> (raw)
Hi
This devices savevm support is "Not Even Wrong". Just remove it.
It has never work for sure.
Anthony, please apply.
Later, Juan.
Juan Quintela (3):
vmstate: remove grackle_pci savevm code
vmstate: remove uninorth savevm code
gt64xxx: remove savevm support
hw/grackle_pci.c | 19 -------------------
hw/gt64xxx.c | 21 ---------------------
hw/unin_pci.c | 21 ---------------------
3 files changed, 0 insertions(+), 61 deletions(-)
--
1.7.4
next reply other threads:[~2011-02-24 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 14:17 Juan Quintela [this message]
2011-02-24 14:17 ` [Qemu-devel] [PATCH 1/3] vmstate: remove grackle_pci savevm code Juan Quintela
2011-02-24 14:17 ` [Qemu-devel] [PATCH 2/3] vmstate: remove uninorth " Juan Quintela
2011-02-24 14:17 ` [Qemu-devel] [PATCH 3/3] gt64xxx: remove savevm support Juan Quintela
2011-03-06 19:11 ` [Qemu-devel] [PATCH 0/3] Remove wrong savevm sections Aurelien Jarno
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=cover.1298556891.git.quintela@redhat.com \
--to=quintela@redhat.com \
--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).