From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Jonathan Cameron via <qemu-devel@nongnu.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH 1/2] pci-bridge/xio3130_upstream: Fix error handling
Date: Fri, 18 Feb 2022 10:31:56 +0000 [thread overview]
Message-ID: <20220218103156.00002583@huawei.com> (raw)
In-Reply-To: <20220218102303.7061-1-Jonathan.Cameron@huawei.com>
On Fri, 18 Feb 2022 10:23:02 +0000
Jonathan Cameron via <qemu-devel@nongnu.org> wrote:
> Goto label is incorrect so msi cleanup would not occur if there is
> an error in the ssvid initialization.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
+Cc: Linuxarm@huawei.com Turns out you get a weird result if you miss
a space in your git send-email command. Apologies to Michael for scrambling
his email address as a result!
> ---
> Noticed whilst working on equivalent CXL upstream switch port.
>
> hw/pci-bridge/xio3130_upstream.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/pci-bridge/xio3130_upstream.c b/hw/pci-bridge/xio3130_upstream.c
> index 5cd3af4fbc..5ff46ef050 100644
> --- a/hw/pci-bridge/xio3130_upstream.c
> +++ b/hw/pci-bridge/xio3130_upstream.c
> @@ -75,7 +75,7 @@ static void xio3130_upstream_realize(PCIDevice *d, Error **errp)
> XIO3130_SSVID_SVID, XIO3130_SSVID_SSID,
> errp);
> if (rc < 0) {
> - goto err_bridge;
> + goto err_msi;
> }
>
> rc = pcie_cap_init(d, XIO3130_EXP_OFFSET, PCI_EXP_TYPE_UPSTREAM,
prev parent reply other threads:[~2022-02-18 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 10:23 [PATCH 1/2] pci-bridge/xio3130_upstream: Fix error handling Jonathan Cameron via
2022-02-18 10:23 ` [PATCH 2/2] pci-bridge/xio3130_downstream: " Jonathan Cameron via
2022-02-18 10:31 ` Jonathan Cameron via [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=20220218103156.00002583@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.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;
as well as URLs for NNTP newsgroup(s).