From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [RfC PATCH 1/2] qdev/pci: make PCIDevice->devfn uint32_t
Date: Tue, 28 Jul 2009 12:24:23 +0200 [thread overview]
Message-ID: <1248776664-4321-2-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1248776664-4321-1-git-send-email-kraxel@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/pci.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/pci.h b/hw/pci.h
index cbfea6a..a2ec16a 100644
--- a/hw/pci.h
+++ b/hw/pci.h
@@ -177,7 +177,7 @@ struct PCIDevice {
/* the following fields are read only */
PCIBus *bus;
- int devfn;
+ uint32_t devfn;
char name[64];
PCIIORegion io_regions[PCI_NUM_REGIONS];
--
1.6.2.5
next prev parent reply other threads:[~2009-07-28 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 10:24 [Qemu-devel] [RfC PATCH 0/2] qdev: property macros Gerd Hoffmann
2009-07-28 10:24 ` Gerd Hoffmann [this message]
2009-07-28 10:24 ` [Qemu-devel] [RfC PATCH 2/2] qdev/prop: macros for creating typechecked properties Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 16:21 [Qemu-devel] [RfC PATCH 0/2] qdev: property macros Gerd Hoffmann
2009-07-28 16:21 ` [Qemu-devel] [RfC PATCH 1/2] qdev/pci: make PCIDevice->devfn uint32_t Gerd Hoffmann
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=1248776664-4321-2-git-send-email-kraxel@redhat.com \
--to=kraxel@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).