From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>, Jakub Kicinski <kuba@kernel.org>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] net: dsa: Simplify with scoped for each OF child loop
Date: Thu, 22 Aug 2024 16:39:38 +0200 [thread overview]
Message-ID: <d44d2e53-6684-4fe5-bcc3-60d387044b63@kernel.org> (raw)
In-Reply-To: <2d67e112-75a0-3111-3f3a-91e6a982652f@huawei.com>
On 22/08/2024 04:07, Jinjie Ruan wrote:
>
>
> On 2024/8/22 8:18, Jakub Kicinski wrote:
>> On Tue, 20 Aug 2024 14:58:04 +0800 Jinjie Ruan wrote:
>>> Use scoped for_each_available_child_of_node_scoped() when iterating over
>>> device nodes to make code a bit simpler.
>>
>> Could you add more info here that confirms this works with gotos?
>> I don't recall the details but I thought sometimes the scoped
>> constructs don't do well with gotos. I checked 5 random uses
>> of this loop and 4 of them didn't have gotos.
>
> Hi, Jakub
>
>>From what I understand, for_each_available_child_of_node_scoped() is not
> related to gotos, it only let the iterating child node self-declared and
> automatic release, so the of_node_put(iterating_child_node) can be removed.
>
> For example, the following use case has goto and use this macro:
>
> Link:
> https://lore.kernel.org/all/20240813-b4-cleanup-h-of-node-put-other-v1-6-cfb67323a95c@linaro.org/
Jinjie,
You started this after me, shortly after my series, taking the commit
msgs and subjects, and even using my work as reference or explanation of
your patches. Basically you just copy-paste. That's ok, thouogh, but you
could at least Cc me to tell me that you are doing it to avoid
duplication. That would be nice... And you could *try to* understand
what you are doing, so you can answer to such concerns as Jakub raised.
Otherwise how can we know that your code is correct?
Jakub,
Scoped uses in-place variable declarations, thus earlier jumps over it
are not allowed. The code I was converting did not have such jumps, so
was fine. Not sure if this is the case here, because Jinjie Ruan should
have checked it and explained that it is safe.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-22 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 6:58 [PATCH -next] net: dsa: Simplify with scoped for each OF child loop Jinjie Ruan
2024-08-22 0:18 ` Jakub Kicinski
2024-08-22 2:07 ` Jinjie Ruan
2024-08-22 14:39 ` Krzysztof Kozlowski [this message]
2024-08-22 15:05 ` Jakub Kicinski
2024-08-23 2:20 ` Jinjie Ruan
2024-08-22 14:51 ` Jakub Kicinski
2024-08-23 2:22 ` Jinjie Ruan
2024-08-23 6:35 ` Jinjie Ruan
2024-08-25 23:28 ` Andrew Lunn
2024-08-26 3:52 ` Jinjie Ruan
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=d44d2e53-6684-4fe5-bcc3-60d387044b63@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ruanjinjie@huawei.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).