From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>
Cc: Andrew Lunn <andrew@lunn.ch>, <kernel@pengutronix.de>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: [PATCH net-next v1 3/6] net: usb: lan78xx: Use action-specific label in lan78xx_mac_reset
Date: Mon, 16 Dec 2024 14:13:03 +0100 [thread overview]
Message-ID: <7d777a2b-f7f0-49c5-86d2-9ac36a351ab9@intel.com> (raw)
In-Reply-To: <20241216120941.1690908-4-o.rempel@pengutronix.de>
On 12/16/2024 1:09 PM, Oleksij Rempel wrote:
[...]
> if (ret < 0)
> - goto done;
> + goto exit_unlock;
>
> ret = lan78xx_read_reg(dev, MAC_CR, &val);
> if (ret < 0)
> - goto done;
> + goto exit_unlock;
>
> val |= MAC_CR_RST_;
> ret = lan78xx_write_reg(dev, MAC_CR, val);
> if (ret < 0)
> - goto done;
> + goto exit_unlock;
>
> /* Wait for the reset to complete before allowing any further
> * MAC register accesses otherwise the MAC may lock up.
> @@ -1621,16 +1621,16 @@ static int lan78xx_mac_reset(struct lan78xx_net *dev)
> do {
> ret = lan78xx_read_reg(dev, MAC_CR, &val);
> if (ret < 0)
> - goto done;
> + goto exit_unlock;
>
> if (!(val & MAC_CR_RST_)) {
> ret = 0;
> - goto done;
> + goto exit_unlock;
> }
> } while (!time_after(jiffies, start_time + HZ));
>
> ret = -ETIMEDOUT;
> -done:
> +exit_unlock:
> mutex_unlock(&dev->phy_mutex);
>
> return ret;
Nice cleanup, now the label indicates what it does.
Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
next prev parent reply other threads:[~2024-12-16 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 12:09 [PATCH net-next v1 0/6] lan78xx: Preparations for PHYlink Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 1/6] net: usb: lan78xx: Add error handling to lan78xx_get_regs Oleksij Rempel
2024-12-16 13:07 ` Mateusz Polchlopek
2024-12-16 13:19 ` Oleksij Rempel
2024-12-16 13:35 ` Mateusz Polchlopek
2024-12-16 12:09 ` [PATCH net-next v1 2/6] net: usb: lan78xx: Use ETIMEDOUT instead of ETIME in lan78xx_stop_hw Oleksij Rempel
2024-12-16 13:08 ` Mateusz Polchlopek
2024-12-16 12:09 ` [PATCH net-next v1 3/6] net: usb: lan78xx: Use action-specific label in lan78xx_mac_reset Oleksij Rempel
2024-12-16 13:13 ` Mateusz Polchlopek [this message]
2024-12-16 12:09 ` [PATCH net-next v1 4/6] net: usb: lan78xx: rename phy_mutex to mdiobus_mutex Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 5/6] net: usb: lan78xx: remove PHY register access from ethtool get_regs Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 6/6] net: usb: lan78xx: Improve error handling in WoL operations Oleksij Rempel
2024-12-18 4:10 ` [PATCH net-next v1 0/6] lan78xx: Preparations for PHYlink patchwork-bot+netdevbpf
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=7d777a2b-f7f0-49c5-86d2-9ac36a351ab9@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=woojung.huh@microchip.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®