From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>, patches@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/4] Fix pxa2xx/strongarm missing vmstate
Date: Thu, 26 Jun 2014 12:42:42 +0100 [thread overview]
Message-ID: <1403782966-20457-1-git-send-email-peter.maydell@linaro.org> (raw)
This patchseries fixes some cases for pxa2xx and strongarm
where we'd defined a vmstate struct but forgotten to actually
register it (caught by new warnings in clang 3.4).
As a prerequisite (suggested by Peter Crosthwaite) we clean
up the handling of GPSR/GPCR reads (which are unpredictable)
so we can avoid having bogus device state in the vmstate.
Peter Maydell (4):
hw/arm/strongarm: Fix handling of GPSR/GPCR reads
hw/arm/strongarm: Wire up missing GPIO and PPC vmstate
hw/arm/pxa2xx_gpio: Fix handling of GPSR/GPCR reads
hw/arm/pxa2xx_gpio: Correct and register vmstate
hw/arm/pxa2xx_gpio.c | 17 ++++++++---------
hw/arm/strongarm.c | 18 ++++++++++--------
2 files changed, 18 insertions(+), 17 deletions(-)
--
1.9.2
next reply other threads:[~2014-06-26 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 11:42 Peter Maydell [this message]
2014-06-26 11:42 ` [Qemu-devel] [PATCH v2 1/4] hw/arm/strongarm: Fix handling of GPSR/GPCR reads Peter Maydell
2014-06-26 11:42 ` [Qemu-devel] [PATCH v2 2/4] hw/arm/strongarm: Wire up missing GPIO and PPC vmstate Peter Maydell
2014-06-26 11:42 ` [Qemu-devel] [PATCH v2 3/4] hw/arm/pxa2xx_gpio: Fix handling of GPSR/GPCR reads Peter Maydell
2014-06-26 11:42 ` [Qemu-devel] [PATCH v2 4/4] hw/arm/pxa2xx_gpio: Correct and register vmstate Peter Maydell
2014-06-27 0:21 ` [Qemu-devel] [PATCH v2 0/4] Fix pxa2xx/strongarm missing vmstate Peter Crosthwaite
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=1403782966-20457-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=patches@linaro.org \
--cc=peter.crosthwaite@xilinx.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).