From: "Andreas Färber" <afaerber@suse.de>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] piix: use type-safe cast instead of directly access of parent dev
Date: Fri, 14 Jun 2013 11:20:55 +0200 [thread overview]
Message-ID: <51BAE077.3000600@suse.de> (raw)
In-Reply-To: <1371192585-536-1-git-send-email-hutao@cn.fujitsu.com>
Hi,
Am 14.06.2013 08:49, schrieb Hu Tao:
> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
> ---
> hw/pci-host/piix.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
> index f9e68c3..ba9a8f0 100644
> --- a/hw/pci-host/piix.c
> +++ b/hw/pci-host/piix.c
> @@ -121,22 +121,24 @@ static int pci_slot_get_pirq(PCIDevice *pci_dev, int pci_intx)
> static void i440fx_update_memory_mappings(PCII440FXState *d)
> {
> int i;
> + PCIDevice *pd = PCI_DEVICE(d);
>
> memory_region_transaction_begin();
> for (i = 0; i < 13; i++) {
> pam_update(&d->pam_regions[i], i,
> - d->dev.config[I440FX_PAM + ((i + 1) / 2)]);
> + pd->config[I440FX_PAM + ((i + 1) / 2)]);
[snip]
These two patches will likely conflict with Peter C.'s recent PCI
patchset doing the same thing.
They look okay, although in one case changing to "dev" variable will
force yet another change when later switching to QOM realize with
DeviceState *dev.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-06-14 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 6:49 [Qemu-devel] [PATCH 1/2] piix: use type-safe cast instead of directly access of parent dev Hu Tao
2013-06-14 6:49 ` [Qemu-devel] [PATCH 2/2] q35: " Hu Tao
2013-06-14 9:20 ` Andreas Färber [this message]
2013-06-17 1:56 ` [Qemu-devel] [PATCH 1/2] piix: " Hu Tao
2013-06-17 3:27 ` Hu Tao
2013-06-17 8:14 ` Peter Crosthwaite
2013-06-17 8:43 ` Hu Tao
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=51BAE077.3000600@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=hutao@cn.fujitsu.com \
--cc=mst@redhat.com \
--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).