From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] msi: Fix copy&paste mistake in msi_uninit
Date: Wed, 8 Jun 2011 21:53:47 +0300 [thread overview]
Message-ID: <20110608185308.GA30805@redhat.com> (raw)
In-Reply-To: <4DEE5F3C.6030104@siemens.com>
On Tue, Jun 07, 2011 at 07:26:20PM +0200, Jan Kiszka wrote:
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Applied, thanks!
> ---
> hw/msi.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/msi.c b/hw/msi.c
> index b087fe5..e8c5607 100644
> --- a/hw/msi.c
> +++ b/hw/msi.c
> @@ -172,7 +172,7 @@ void msi_uninit(struct PCIDevice *dev)
> }
> flags = pci_get_word(dev->config + msi_flags_off(dev));
> cap_size = msi_cap_sizeof(flags);
> - pci_del_capability(dev, PCI_CAP_ID_MSIX, cap_size);
> + pci_del_capability(dev, PCI_CAP_ID_MSI, cap_size);
> dev->cap_present &= ~QEMU_PCI_CAP_MSI;
>
> MSI_DEV_PRINTF(dev, "uninit\n");
> --
> 1.7.1
prev parent reply other threads:[~2011-06-08 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 17:26 [Qemu-devel] [PATCH] msi: Fix copy&paste mistake in msi_uninit Jan Kiszka
2011-06-08 18:53 ` Michael S. Tsirkin [this message]
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=20110608185308.GA30805@redhat.com \
--to=mst@redhat.com \
--cc=jan.kiszka@siemens.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).