From: Jakub Kicinski <kuba@kernel.org>
To: jacky_chou@aspeedtech.com
Cc: Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, horms@kernel.org,
edumazet@google.com, davem@davemloft.net, pabeni@redhat.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org, andrew@lunn.ch
Subject: Re: [net-next,v3,08/15] net: ftgmac100: Move NCSI probe code into a helper
Date: Tue, 3 Feb 2026 19:34:21 -0800 [thread overview]
Message-ID: <20260204033421.1665426-1-kuba@kernel.org> (raw)
In-Reply-To: <20260202-ftgmac-cleanup-v3-8-6a6a8d45280a@aspeedtech.com>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net: ftgmac100: Move NCSI probe code into a helper
This commit refactors ftgmac100_probe() by extracting NCSI-specific probe
code into a new helper function ftgmac100_probe_ncsi(). The commit message
states "No functional change intended."
> diff --git a/drivers/net/ethernet/faraday/ftgmac100.c b/drivers/net/ethernet/faraday/ftgmac100.c
> index e511d6d5f7c2..9d8256d4d368 100644
> --- a/drivers/net/ethernet/faraday/ftgmac100.c
> +++ b/drivers/net/ethernet/faraday/ftgmac100.c
> @@ -1839,6 +1839,39 @@ static bool ftgmac100_has_child_node(struct device_node *np, const char *name)
> return ret;
> }
>
> +static int ftgmac100_probe_ncsi(struct net_device *netdev,
> + struct ftgmac100 *priv,
> + struct platform_device *pdev)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + struct phy_device *phydev;
> + int err;
> +
> + if (!IS_ENABLED(CONFIG_NET_NCSI)) {
> + dev_err(&pdev->dev, "NCSI stack not enabled\n");
> + return -EINVAL;
> + }
> +
> + dev_info(&pdev->dev, "Using NCSI interface\n");
> + priv->use_ncsi = true;
> + priv->ndev = ncsi_register_dev(netdev, ftgmac100_ncsi_handler);
> + if (!priv->ndev)
> + return -EINVAL;
> +
> + phydev = fixed_phy_register(&ncsi_phy_status, np);
> + if (IS_ERR(phydev)) {
> + dev_err(&pdev->dev, "failed to register fixed PHY device\n");
> + return PTR_ERR(phydev);
If fixed_phy_register() fails here, doesn't priv->ndev leak? The NCSI device
was registered via ncsi_register_dev() above, but this error path returns
without calling ncsi_unregister_dev().
> + }
> + err = phy_connect_direct(netdev, phydev, ftgmac100_adjust_link,
> + PHY_INTERFACE_MODE_RMII);
> + if (err) {
> + dev_err(&pdev->dev, "Connecting PHY failed\n");
> + fixed_phy_unregister(phydev);
> + }
> + return err;
Similarly, if phy_connect_direct() fails, fixed_phy_unregister() is called
but ncsi_unregister_dev(priv->ndev) is not.
[ ... ]
> @@ -1928,32 +1960,9 @@ static int ftgmac100_probe(struct platform_device *pdev)
> }
>
> if (np && of_get_property(np, "use-ncsi", NULL)) {
> - if (!IS_ENABLED(CONFIG_NET_NCSI)) {
> - dev_err(&pdev->dev, "NCSI stack not enabled\n");
> - err = -EINVAL;
> - goto err_phy_connect;
[ ... ]
> - phydev = fixed_phy_register(&ncsi_phy_status, np);
> - if (IS_ERR(phydev)) {
> - dev_err(&pdev->dev, "failed to register fixed PHY device\n");
> - err = PTR_ERR(phydev);
> - goto err_phy_connect;
The old code jumped to err_phy_connect on failure, which falls through to
err_ncsi_dev where ncsi_unregister_dev(priv->ndev) is called.
> + err = ftgmac100_probe_ncsi(netdev, priv, pdev);
> + if (err)
> + goto err_setup_mdio;
The new code jumps to err_setup_mdio, which skips the err_ncsi_dev label
entirely. Combined with the helper not cleaning up priv->ndev on its error
paths, this appears to be a behavioral change from the original code.
--
pw-bot: cr
next prev parent reply other threads:[~2026-02-04 3:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 6:56 [PATCH net-next v3 00/15] net: ftgmac100: Various probe cleanups Jacky Chou
2026-02-02 6:56 ` [PATCH net-next v3 01/15] net: ftgmac100: List all compatibles Jacky Chou
2026-02-02 6:56 ` [PATCH net-next v3 02/15] net: ftgmac100: Add match data containing MAC ID Jacky Chou
2026-02-02 6:56 ` [PATCH net-next v3 03/15] net: ftgmac100: Replace all of_device_is_compatible() Jacky Chou
2026-02-02 6:56 ` [PATCH net-next v3 04/15] net: ftgmac100: Use devm_alloc_etherdev() Jacky Chou
2026-02-02 6:56 ` [PATCH net-next v3 05/15] net: ftgmac100: Use devm_request_memory_region/devm_ioremap Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 06/15] net: ftgmac100: Use devm_clk_get_enabled Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 07/15] net: ftgmac100: Simplify error handling for ftgmac100_initial_mac Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 08/15] net: ftgmac100: Move NCSI probe code into a helper Jacky Chou
2026-02-04 3:34 ` Jakub Kicinski [this message]
2026-02-02 6:57 ` [PATCH net-next v3 09/15] net: ftgmac100: Always register the MDIO bus when it exists Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 10/15] net: ftgmac100: Simplify legacy MDIO setup Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 11/15] net: ftgmac100: Move DT probe into a helper Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 12/15] net: ftgmac100: Remove redundant PHY_POLL Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 13/15] net: ftgmac100: Simplify condition on HW arbitration Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 14/15] net: ftgmac100: Fix wrong netif_napi_del in release Jacky Chou
2026-02-02 6:57 ` [PATCH net-next v3 15/15] net: ftgmac100: Use devm_mdiobus_alloc/devm_of_mdiobus_register Jacky Chou
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=20260204033421.1665426-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacky_chou@aspeedtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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