From: Zijun Hu <zijun_hu@icloud.com>
To: Simon Horman <horms@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH net-next] net: wan: framer: Simplify API framer_provider_simple_of_xlate() implementation
Date: Fri, 13 Dec 2024 18:57:15 +0800 [thread overview]
Message-ID: <692ac4bc-aa97-4fea-9f40-bad7339e9474@icloud.com> (raw)
In-Reply-To: <20241212164149.GB73795@kernel.org>
On 2024/12/13 00:41, Simon Horman wrote:
>> struct framer *framer_provider_simple_of_xlate(struct device *dev,
>> const struct of_phandle_args *args)
>> {
>> - struct class_dev_iter iter;
>> - struct framer *framer;
>> -
>> - class_dev_iter_init(&iter, &framer_class, NULL, NULL);
>> - while ((dev = class_dev_iter_next(&iter))) {
>> - framer = dev_to_framer(dev);
>> - if (args->np != framer->dev.of_node)
>> - continue;
>> + struct device *target_dev;
>>
>> - class_dev_iter_exit(&iter);
>> - return framer;
>> + target_dev = class_find_device_by_of_node(&framer_class, args->np);
>> + if (target_dev) {
>> + put_device(target_dev);
>> + return dev_to_framer(target_dev);
>> }
>>
>> - class_dev_iter_exit(&iter);
>> return ERR_PTR(-ENODEV);
> Hi Zijun Hu,
>
> FWIIW, I think it would be more idiomatic to have the non-error path in the
> main flow of execution, something like this (completely untested!):
>
> target_dev = class_find_device_by_of_node(&framer_class, args->np);
> if (!target_dev)
> return ERR_PTR(-ENODEV);
>
> put_device(target_dev);
> return dev_to_framer(target_dev);
>
thank you Simon for code review.
good suggestion. let me take it in v2.
> Also, is it safe to put_device(target_dev) before
> passing target_dev to dev_to_framer() ?
Successful class_find_device_by_of_node() invocation will increase the
refcount of @target_dev, so i put_device() here to keep the same logic
as original.
thank you.
prev parent reply other threads:[~2024-12-13 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:28 Zijun Hu
2024-12-12 16:41 ` Simon Horman
2024-12-13 10:57 ` Zijun Hu [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=692ac4bc-aa97-4fea-9f40-bad7339e9474@icloud.com \
--to=zijun_hu@icloud.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_zijuhu@quicinc.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
all inboxes | Powered by JetHome®