From: Alex Williamson <alex.williamson@redhat.com>
To: Wei Yongjun <yjwei@cn.fujitsu.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] [qemu-kvm-next-tree] fix compile error of hw/device-assignment.c
Date: Thu, 09 Dec 2010 06:38:20 -0700 [thread overview]
Message-ID: <1291901900.17031.24.camel@x201> (raw)
In-Reply-To: <4D007A82.8030604@cn.fujitsu.com>
On Thu, 2010-12-09 at 14:43 +0800, Wei Yongjun wrote:
> Fix the following compile error in next tree:
> CC x86_64-softmmu/device-assignment.o
> hw/device-assignment.c: In function ‘assigned_device_pci_cap_init’:
> hw/device-assignment.c:1463: error: ‘PCI_PM_CTRL_NO_SOFT_RST’ undeclared (first use in this function)
> hw/device-assignment.c:1463: error: (Each undeclared identifier is reported only once
> hw/device-assignment.c:1463: error: for each function it appears in.)
>
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
Interesting, my build environment was finding RST somewhere. Thanks for
the fix.
Acked-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> hw/device-assignment.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/device-assignment.c b/hw/device-assignment.c
> index 50c6408..8446cd4 100644
> --- a/hw/device-assignment.c
> +++ b/hw/device-assignment.c
> @@ -1460,7 +1460,7 @@ static int assigned_device_pci_cap_init(PCIDevice *pci_dev)
> /* assign_device will bring the device up to D0, so we don't need
> * to worry about doing that ourselves here. */
> pci_set_word(pci_dev->config + pos + PCI_PM_CTRL,
> - PCI_PM_CTRL_NO_SOFT_RST);
> + PCI_PM_CTRL_NO_SOFT_RESET);
>
> pci_set_byte(pci_dev->config + pos + PCI_PM_PPB_EXTENSIONS, 0);
> pci_set_byte(pci_dev->config + pos + PCI_PM_DATA_REGISTER, 0);
next prev parent reply other threads:[~2010-12-09 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 6:43 [PATCH] [qemu-kvm-next-tree] fix compile error of hw/device-assignment.c Wei Yongjun
2010-12-09 13:38 ` Alex Williamson [this message]
2010-12-13 12:04 ` Avi Kivity
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=1291901900.17031.24.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yjwei@cn.fujitsu.com \
/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