From: Markus Elfring <Markus.Elfring@web.de>
To: Jim Quinlan <james.quinlan@broadcom.com>,
linux-pci@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
Bjorn Helgaas <bhelgaas@google.com>,
Cyril Brulebois <kibi@debian.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Stanimir Varbanov <svarbanov@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH 2/8] PCI: brcmstb: Use "clk_out" error path label
Date: Wed, 3 Jul 2024 20:45:34 +0200 [thread overview]
Message-ID: <f90b597d-1e0f-497f-b092-3cb4d5f9602d@web.de> (raw)
In-Reply-To: <20240628205430.24775-3-james.quinlan@broadcom.com>
> [-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
Can improved adjustments be provided as regular diff data (without an extra attachment)?
> Instead of invoking "clk_disable_unprepare(pcie->clk)" in
> a number of error paths.
* Can a wording approach (like the following) be a better change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n45
Add a jump target so that a bit of exception handling can be better reused
at the end of this function implementation.
* How do you think about to use a summary phrase like
“Use more common error handling code in brcm_pcie_probe()”?
…
> +++ b/drivers/pci/controller/pcie-brcmstb.c
…
> ret = reset_control_reset(pcie->rescal);
> - if (ret)
> + if (ret) {
> dev_err(&pdev->dev, "failed to deassert 'rescal'\n");
> + goto clk_out;
> + }
>
> ret = brcm_phy_start(pcie);
…
Does this software update complete the exception handling?
Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
…
> @@ -1676,6 +1677,9 @@ static int brcm_pcie_probe(struct platform_device *pdev)
>
> return 0;
>
> +clk_out:
> + clk_disable_unprepare(pcie->clk);
> + return ret;
> fail:
…
I suggest to add a blank line before the second label.
Regards,
Markus
next prev parent reply other threads:[~2024-07-03 18:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 20:54 [PATCH v1 0/8] PCI: brcnstb: Enable STB 7712 SOC Jim Quinlan
2024-06-28 20:54 ` Jim Quinlan
2024-06-28 20:54 ` [PATCH v1 1/8] dt-bindings: PCI: Add Broadcom STB 7712 SOC, update maintainter Jim Quinlan
2024-07-01 9:12 ` Krzysztof Kozlowski
2024-07-02 21:57 ` Jim Quinlan
2024-07-03 4:33 ` Krzysztof Kozlowski
2024-07-01 19:47 ` Bjorn Helgaas
2024-06-28 20:54 ` [PATCH v1 2/8] PCI: brcmstb: Use "clk_out" error path label Jim Quinlan
2024-07-01 19:49 ` Bjorn Helgaas
2024-07-03 18:45 ` Markus Elfring [this message]
2024-06-28 20:54 ` [PATCH v1 3/8] PCI: brcmstb: Use bridge reset if available Jim Quinlan
2024-07-02 12:59 ` Stanimir Varbanov
2024-07-02 18:36 ` Jim Quinlan
2024-07-03 13:09 ` Stanimir Varbanov
2024-06-28 20:54 ` [PATCH v1 4/8] PCI: brcmstb: Use swinit " Jim Quinlan
2024-07-01 9:48 ` Philipp Zabel
2024-07-02 13:02 ` Stanimir Varbanov
2024-06-28 20:54 ` [PATCH v1 5/8] PCI: brcmstb: Two more register offsets vary by SOC Jim Quinlan
2024-07-01 3:23 ` kernel test robot
2024-07-01 17:32 ` Bjorn Helgaas
2024-06-28 20:54 ` [PATCH v1 6/8] PCI: brcmstb: Don't conflate the reset rescal with phy ctrl Jim Quinlan
2024-07-02 13:10 ` Stanimir Varbanov
2024-07-02 17:59 ` Jim Quinlan
2024-07-03 12:38 ` Stanimir Varbanov
2024-06-28 20:54 ` [PATCH v1 7/8] PCI: brcmstb: Refactor for chips with many regular inbound BARs Jim Quinlan
2024-06-28 20:54 ` [PATCH v1 8/8] PCI: brcmstb: Enable 7712 SOCs Jim Quinlan
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=f90b597d-1e0f-497f-b092-3cb4d5f9602d@web.de \
--to=markus.elfring@web.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=james.quinlan@broadcom.com \
--cc=kibi@debian.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lpieralisi@kernel.org \
--cc=nsaenz@kernel.org \
--cc=robh@kernel.org \
--cc=svarbanov@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.