From: "Kadosh, MoriyaX" <moriyax.kadosh@intel.com>
To: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
KhaiWenTan <khai.wen.tan@linux.intel.com>,
<anthony.l.nguyen@intel.com>, <przemyslaw.kitszel@intel.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <faizal.abdul.rahim@intel.com>,
<hong.aun.looi@intel.com>, <hector.blanco.alcaine@intel.com>,
<khai.wen.tan@intel.com>,
Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 3/4] igc: replace goto out with direct returns in igc_config_fc_after_link_up()
Date: Mon, 22 Jun 2026 11:11:26 +0300 [thread overview]
Message-ID: <db5a9f18-198f-4c88-bcba-ad408252c1a4@intel.com> (raw)
In-Reply-To: <58af982a-1531-43f8-934c-e83b45111b1f@intel.com>
On 14/06/2026 10:17, Ruinskiy, Dima wrote:
> On 08/05/2026 0:47, KhaiWenTan wrote:
>> From: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
>>
>> The out: label only returns ret_val with no cleanup. The kernel coding
>> style guide states: "If there is no cleanup needed then just return
>> directly." (Documentation/process/coding-style.rst, section 7).
>>
>> This improves readability ahead of a subsequent patch that introduces a
>> new goto label in this function.
>>
>> No functional change.
>>
>> Reviewed-by: Looi Hong Aun <hong.aun.looi@intel.com>
>> Signed-off-by: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
>> Signed-off-by: Khai Wen Tan <khai.wen.tan@linux.intel.com>
>> ---
>> drivers/net/ethernet/intel/igc/igc_mac.c | 15 +++++++--------
>> 1 file changed, 7 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/igc/igc_mac.c b/drivers/net/
>> ethernet/intel/igc/igc_mac.c
>> index 142beb9ae557..0a3d3f357505 100644
>> --- a/drivers/net/ethernet/intel/igc/igc_mac.c
>> +++ b/drivers/net/ethernet/intel/igc/igc_mac.c
>> @@ -458,15 +458,15 @@ s32 igc_config_fc_after_link_up(struct igc_hw *hw)
>> ret_val = hw->phy.ops.read_reg(hw, PHY_STATUS,
>> &mii_status_reg);
>> if (ret_val)
>> - goto out;
>> + return ret_val;
>> ret_val = hw->phy.ops.read_reg(hw, PHY_STATUS,
>> &mii_status_reg);
>> if (ret_val)
>> - goto out;
>> + return ret_val;
>> if (!(mii_status_reg & MII_SR_AUTONEG_COMPLETE)) {
>> hw_dbg("Copper PHY and Auto Neg has not completed.\n");
>> - goto out;
>> + return ret_val;
>> }
>> /* The AutoNeg process has completed, so we now need to
>> @@ -478,11 +478,11 @@ s32 igc_config_fc_after_link_up(struct igc_hw *hw)
>> ret_val = hw->phy.ops.read_reg(hw, PHY_AUTONEG_ADV,
>> &mii_nway_adv_reg);
>> if (ret_val)
>> - goto out;
>> + return ret_val;
>> ret_val = hw->phy.ops.read_reg(hw, PHY_LP_ABILITY,
>> &mii_nway_lp_ability_reg);
>> if (ret_val)
>> - goto out;
>> + return ret_val;
>> /* Two bits in the Auto Negotiation Advertisement Register
>> * (Address 4) and two bits in the Auto Negotiation Base
>> * Page Ability Register (Address 5) determine flow control
>> @@ -598,7 +598,7 @@ s32 igc_config_fc_after_link_up(struct igc_hw *hw)
>> ret_val = hw->mac.ops.get_speed_and_duplex(hw, &speed, &duplex);
>> if (ret_val) {
>> hw_dbg("Error getting link speed and duplex\n");
>> - goto out;
>> + return ret_val;
>> }
>> if (duplex == HALF_DUPLEX)
>> @@ -610,10 +610,9 @@ s32 igc_config_fc_after_link_up(struct igc_hw *hw)
>> ret_val = igc_force_mac_fc(hw);
>> if (ret_val) {
>> hw_dbg("Error forcing flow control settings\n");
>> - goto out;
>> + return ret_val;
>> }
>> -out:
>> return ret_val;
>> }
> Reviewed-by: Dima Ruinskiy <dima.ruinskiy@intel.com>
Tested-by: Moriya Kadosh <moriyax.kadosh@intel.com>
next prev parent reply other threads:[~2026-06-22 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 21:47 [PATCH iwl-next v5 0/4] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-05-07 21:47 ` [PATCH iwl-next v5 1/4] igc: remove unused autoneg_failed field KhaiWenTan
2026-06-14 7:16 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-06-22 8:10 ` Kadosh, MoriyaX
2026-06-15 8:22 ` Kwapulinski, Piotr
2026-05-07 21:47 ` [PATCH iwl-next v5 2/4] igc: move autoneg-enabled settings into igc_handle_autoneg_enabled() KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-06-22 8:08 ` Kadosh, MoriyaX
2026-05-07 21:47 ` [PATCH iwl-next v5 3/4] igc: replace goto out with direct returns in igc_config_fc_after_link_up() KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-06-22 8:11 ` Kadosh, MoriyaX [this message]
2026-05-07 21:47 ` [PATCH iwl-next v5 4/4] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-06-22 8:12 ` Kadosh, MoriyaX
2026-05-11 16:28 ` [PATCH iwl-next v5 0/4] " Simon Horman
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=db5a9f18-198f-4c88-bcba-ad408252c1a4@intel.com \
--to=moriyax.kadosh@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=faizal.abdul.rahim@intel.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=hector.blanco.alcaine@intel.com \
--cc=hong.aun.looi@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=khai.wen.tan@intel.com \
--cc=khai.wen.tan@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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