From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 9/9] pvpanic: use FWCfgState explicitly
Date: Tue, 4 Jun 2013 11:08:07 +0300 [thread overview]
Message-ID: <1370202787-3712-10-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1370202787-3712-1-git-send-email-mst@redhat.com>
Use the type-safe FWCfgState structure instead
of the unsafe void *.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
hw/misc/pvpanic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/misc/pvpanic.c b/hw/misc/pvpanic.c
index 159340f..910e44f 100644
--- a/hw/misc/pvpanic.c
+++ b/hw/misc/pvpanic.c
@@ -90,7 +90,7 @@ static int pvpanic_isa_initfn(ISADevice *dev)
{
PVPanicState *s = ISA_PVPANIC_DEVICE(dev);
static bool port_configured;
- void *fw_cfg;
+ FWCfgState *fw_cfg;
memory_region_init_io(&s->io, &pvpanic_ops, s, "pvpanic", 1);
isa_register_ioport(dev, &s->io, s->ioport);
--
MST
next prev parent reply other threads:[~2013-06-04 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 8:07 [Qemu-devel] [PULL 0/9] pci: misc cleanups Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 1/9] q35: set fw_name Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 2/9] dec.c - move to pci-bridge Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 3/9] firmware_abi: move to include/hw/nvram/ Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 4/9] apic: rename apic specific bitopts Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 5/9] refer to FWCfgState explicitly Michael S. Tsirkin
2013-06-04 8:07 ` [Qemu-devel] [PULL 6/9] fw_cfg: move typedef to qemu/typedefs.h Michael S. Tsirkin
2013-06-04 8:08 ` [Qemu-devel] [PULL 7/9] fw_cfg: add API to find FW cfg object Michael S. Tsirkin
2013-06-04 8:08 ` [Qemu-devel] [PULL 8/9] fw_cfg: fw_cfg is a singleton Michael S. Tsirkin
2013-06-04 8:08 ` Michael S. Tsirkin [this message]
2013-06-17 21:17 ` [Qemu-devel] [PULL 0/9] pci: misc cleanups Anthony Liguori
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=1370202787-3712-10-git-send-email-mst@redhat.com \
--to=mst@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).