From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Gatien Chevallier <gatien.chevallier@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] bus: stm32_firewall: Simplify with scoped for each OF child loop
Date: Mon, 5 Jan 2026 10:49:10 +0000 [thread overview]
Message-ID: <20260105104910.00006981@huawei.com> (raw)
In-Reply-To: <20260102125030.65186-4-krzysztof.kozlowski@oss.qualcomm.com>
On Fri, 2 Jan 2026 13:50:32 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> wrote:
> Use scoped for-each loop when iterating over device nodes to make code a
> bit simpler.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
You could throw a __free() in there for firewalls and avoid having
any cleanup at all to do on error (or good path for that matter).
Otherwise LGTM.
Jonathan
> ---
> drivers/bus/stm32_firewall.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/bus/stm32_firewall.c b/drivers/bus/stm32_firewall.c
> index 2fc9761dadec..fae881cea9a0 100644
> --- a/drivers/bus/stm32_firewall.c
> +++ b/drivers/bus/stm32_firewall.c
> @@ -241,7 +241,6 @@ EXPORT_SYMBOL_GPL(stm32_firewall_controller_unregister);
> int stm32_firewall_populate_bus(struct stm32_firewall_controller *firewall_controller)
> {
> struct stm32_firewall *firewalls;
> - struct device_node *child;
> struct device *parent;
> unsigned int i;
> int len;
> @@ -251,25 +250,20 @@ int stm32_firewall_populate_bus(struct stm32_firewall_controller *firewall_contr
>
> dev_dbg(parent, "Populating %s system bus\n", dev_name(firewall_controller->dev));
>
> - for_each_available_child_of_node(dev_of_node(parent), child) {
> + for_each_available_child_of_node_scoped(dev_of_node(parent), child) {
> /* The access-controllers property is mandatory for firewall bus devices */
> len = of_count_phandle_with_args(child, "access-controllers",
> "#access-controller-cells");
> - if (len <= 0) {
> - of_node_put(child);
> + if (len <= 0)
> return -EINVAL;
> - }
>
> firewalls = kcalloc(len, sizeof(*firewalls), GFP_KERNEL);
> - if (!firewalls) {
> - of_node_put(child);
> + if (!firewalls)
> return -ENOMEM;
> - }
>
> err = stm32_firewall_get_firewall(child, firewalls, (unsigned int)len);
> if (err) {
> kfree(firewalls);
> - of_node_put(child);
> return err;
> }
>
next prev parent reply other threads:[~2026-01-05 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 12:50 [PATCH 1/2] bus: qcom-ebi2: Simplify with scoped for each OF child loop Krzysztof Kozlowski
2026-01-02 12:50 ` [PATCH 2/2] bus: stm32_firewall: " Krzysztof Kozlowski
2026-01-02 14:04 ` Konrad Dybcio
2026-01-05 10:49 ` Jonathan Cameron [this message]
2026-01-02 14:04 ` [PATCH 1/2] bus: qcom-ebi2: " Konrad Dybcio
2026-01-03 4:34 ` (subset) " Bjorn Andersson
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=20260105104910.00006981@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=konradybcio@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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