From: Robin Murphy <robin.murphy@arm.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/5] PCI: dwc: Free MSI in the error code path of dw_pcie_host_init()
Date: Thu, 28 Mar 2019 17:08:43 +0000 [thread overview]
Message-ID: <689f8a0f-ba79-da80-d0e3-24ef6814a9aa@arm.com> (raw)
In-Reply-To: <20190318174841.522fb6fd@xhacker.debian>
On 18/03/2019 09:56, Jisheng Zhang wrote:
> If we ever did some msi related initializations, we need to call
> dw_pcie_free_msi() in the error code path.
>
> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> Acked-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
> ---
> drivers/pci/controller/dwc/pcie-designware-host.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> index a71b874ae3c0..585080699675 100644
> --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -483,7 +483,7 @@ int dw_pcie_host_init(struct pcie_port *pp)
> if (pp->ops->host_init) {
> ret = pp->ops->host_init(pp);
> if (ret)
> - goto error;
> + goto err_free_msi;
> }
>
> pp->root_bus_nr = pp->busn->start;
> @@ -497,7 +497,7 @@ int dw_pcie_host_init(struct pcie_port *pp)
>
> ret = pci_scan_root_bus_bridge(bridge);
> if (ret)
> - goto error;
> + goto err_free_msi;
>
> bus = bridge->bus;
>
> @@ -513,6 +513,10 @@ int dw_pcie_host_init(struct pcie_port *pp)
> pci_bus_add_devices(bus);
> return 0;
>
> +err_free_msi:
> + if (IS_ENABLED(CONFIG_PCI_MSI) && pci_msi_enabled() &&
pci_msi_enabled() already has a stub for !CONFIG_PCI_MSI, so you
shouldn't need an explicit IS_ENABLED() here.
Robin.
> + !pp->ops->msi_host_init)
> + dw_pcie_free_msi(pp);
> error:
> pci_free_host_bridge(bridge);
> return ret;
>
next prev parent reply other threads:[~2019-03-28 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:53 [PATCH v3 0/5] PCI: dwc: Support remove Jisheng Zhang
2019-03-18 9:53 ` [PATCH v3 1/5] PCI: dwc: Fix dw_pcie_free_msi() if msi_irq is invalid Jisheng Zhang
2019-03-18 9:54 ` [PATCH v3 2/5] PCI: dwc: Free the page for MSI IRQ in dw_pcie_free_msi() Jisheng Zhang
2019-03-18 10:03 ` Gustavo Pimentel
2019-03-18 9:55 ` PCI: dwc: Free MSI in the error code path of dw_pcie_host_init() Jisheng Zhang
2019-03-18 10:00 ` Jisheng Zhang
2019-03-18 9:56 ` [PATCH v3 3/5] " Jisheng Zhang
2019-03-28 17:08 ` Robin Murphy [this message]
2019-03-29 12:00 ` Jisheng Zhang
2019-03-18 9:57 ` [PATCH v3 4/5] PCI: dwc: Use devm_pci_alloc_host_bridge() to simplify the code Jisheng Zhang
2019-03-18 9:58 ` [PATCH v3 5/5] PCI: dwc: Save root bus for driver remove Jisheng Zhang
2019-03-18 10:09 ` Gustavo Pimentel
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=689f8a0f-ba79-da80-d0e3-24ef6814a9aa@arm.com \
--to=robin.murphy@arm.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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
Powered by JetHome