From: Paolo Abeni <pabeni@redhat.com>
To: Rosen Penev <rosenp@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, jacob.e.keller@intel.com,
horms@kernel.org, sd@queasysnail.net, chunkeey@gmail.com
Subject: Re: [PATCHv2 net-next 8/8] net: ibm: emac: remove all waiting code
Date: Thu, 5 Sep 2024 12:27:43 +0200 [thread overview]
Message-ID: <8fe1d9da-40cc-4537-80ce-6a2855c2dec4@redhat.com> (raw)
In-Reply-To: <20240903194312.12718-9-rosenp@gmail.com>
On 9/3/24 21:42, Rosen Penev wrote:
[...]
> static int emac_wait_deps(struct emac_instance *dev)
Possibly rename the function to something else, as it does not wait anymore?
> @@ -2419,26 +2397,25 @@ static int emac_wait_deps(struct emac_instance *dev)
> deps[EMAC_DEP_MDIO_IDX].phandle = dev->mdio_ph;
> if (dev->blist && dev->blist > emac_boot_list)
> deps[EMAC_DEP_PREV_IDX].phandle = 0xffffffffu;
> - bus_register_notifier(&platform_bus_type, &emac_of_bus_notifier);
> - wait_event_timeout(emac_probe_wait,
> - emac_check_deps(dev, deps),
> - EMAC_PROBE_DEP_TIMEOUT);
> - bus_unregister_notifier(&platform_bus_type, &emac_of_bus_notifier);
> - err = emac_check_deps(dev, deps) ? 0 : -ENODEV;
> +
> + err = emac_check_deps(dev, deps);
> + if (err)
> + return err;
> +
> for (i = 0; i < EMAC_DEP_COUNT; i++) {
> of_node_put(deps[i].node);
> - if (err)
> - platform_device_put(deps[i].ofdev);
> - }
> - if (err == 0) {
> - dev->mal_dev = deps[EMAC_DEP_MAL_IDX].ofdev;
> - dev->zmii_dev = deps[EMAC_DEP_ZMII_IDX].ofdev;
> - dev->rgmii_dev = deps[EMAC_DEP_RGMII_IDX].ofdev;
> - dev->tah_dev = deps[EMAC_DEP_TAH_IDX].ofdev;
> - dev->mdio_dev = deps[EMAC_DEP_MDIO_IDX].ofdev;
> + platform_device_put(deps[i].ofdev);
I'm likely lost, but AFAICS after the patch, on success
platform_device_put() is invoked unconditionally on each deps[] entry,
while before it was called only on failure?!?
/P
prev parent reply other threads:[~2024-09-05 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 19:42 [PATCHv2 net-next 0/8] Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 1/8] net: ibm: emac: use devm for alloc_etherdev Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 2/8] net: ibm: emac: manage emac_irq with devm Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 3/8] net: ibm: emac: use devm for of_iomap Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 4/8] net: ibm: emac: remove mii_bus with devm Rosen Penev
2024-09-05 10:12 ` Paolo Abeni
2024-09-03 19:42 ` [PATCHv2 net-next 5/8] net: ibm: emac: use devm for register_netdev Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 6/8] net: ibm: emac: use netdev's phydev directly Rosen Penev
2024-09-05 10:10 ` Paolo Abeni
2024-09-03 19:42 ` [PATCHv2 net-next 7/8] net: ibm: emac: replace of_get_property Rosen Penev
2024-09-03 19:42 ` [PATCHv2 net-next 8/8] net: ibm: emac: remove all waiting code Rosen Penev
2024-09-05 10:27 ` Paolo Abeni [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=8fe1d9da-40cc-4537-80ce-6a2855c2dec4@redhat.com \
--to=pabeni@redhat.com \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sd@queasysnail.net \
/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®