From: Simon Horman <horms@kernel.org>
To: KhaiWenTan <khai.wen.tan@linux.intel.com>
Cc: 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,
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: [PATCH iwl-next v5 0/4] igc: add support for forcing link speed without autonegotiation
Date: Mon, 11 May 2026 17:28:09 +0100 [thread overview]
Message-ID: <20260511162809.GF27589@horms.kernel.org> (raw)
In-Reply-To: <20260507214706.309984-1-khai.wen.tan@linux.intel.com>
On Fri, May 08, 2026 at 05:47:02AM +0800, KhaiWenTan wrote:
> From: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
>
> This series adds support for forcing 10/100 Mb/s link speed via ethtool
> when autonegotiation is disabled on the igc driver.
>
> Changes in v5:
> - add removal justification to include copper context in commit
> description for igc: remove unused autoneg_failed field (Paul)
> - check that cmd->base.duplex is either DUPLEX_HALF or DUPLEX_FULL
> in igc_ethtool_set_link_ksettings() (Simon)
> - dynamically override hw->fc.current_mode to igc_fc_none during
> link configuration instead of mutating requested_mode (Simon)
>
> Changes in v4:
> - Validate that autoneg is AUTONEG_ENABLE or AUTONEG_DISABLE early
> in igc_ethtool_set_link_ksettings() to avoid passing unexpected
> values to igc_handle_autoneg_disabled(). (Simon Horman)
>
> Changes in v3:
> - Modify condition from "if (duplex == DUPLEX_HALF)" to
> "if (duplex != DUPLEX_FULL)". (Simon Horman)
>
> Changes in v2:
> - When forcing half-duplex, set hw->fc.requested_mode = igc_fc_none,
> since half-duplex cannot support flow control per IEEE 802.3.
> (Simon Horman)
> - Split the original single patch into three patches for clarity:
> patches 1 and 2 are preparatory cleanups; patch 3 carries the
> functional change.
Thanks for your persistence.
For the series:
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: KhaiWenTan <khai.wen.tan@linux.intel.com>
Cc: 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,
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 0/4] igc: add support for forcing link speed without autonegotiation
Date: Mon, 11 May 2026 17:28:09 +0100 [thread overview]
Message-ID: <20260511162809.GF27589@horms.kernel.org> (raw)
In-Reply-To: <20260507214706.309984-1-khai.wen.tan@linux.intel.com>
On Fri, May 08, 2026 at 05:47:02AM +0800, KhaiWenTan wrote:
> From: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
>
> This series adds support for forcing 10/100 Mb/s link speed via ethtool
> when autonegotiation is disabled on the igc driver.
>
> Changes in v5:
> - add removal justification to include copper context in commit
> description for igc: remove unused autoneg_failed field (Paul)
> - check that cmd->base.duplex is either DUPLEX_HALF or DUPLEX_FULL
> in igc_ethtool_set_link_ksettings() (Simon)
> - dynamically override hw->fc.current_mode to igc_fc_none during
> link configuration instead of mutating requested_mode (Simon)
>
> Changes in v4:
> - Validate that autoneg is AUTONEG_ENABLE or AUTONEG_DISABLE early
> in igc_ethtool_set_link_ksettings() to avoid passing unexpected
> values to igc_handle_autoneg_disabled(). (Simon Horman)
>
> Changes in v3:
> - Modify condition from "if (duplex == DUPLEX_HALF)" to
> "if (duplex != DUPLEX_FULL)". (Simon Horman)
>
> Changes in v2:
> - When forcing half-duplex, set hw->fc.requested_mode = igc_fc_none,
> since half-duplex cannot support flow control per IEEE 802.3.
> (Simon Horman)
> - Split the original single patch into three patches for clarity:
> patches 1 and 2 are preparatory cleanups; patch 3 carries the
> functional change.
Thanks for your persistence.
For the series:
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-05-11 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 21:47 [Intel-wired-lan] [PATCH iwl-next v5 0/4] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-05-07 21:47 ` KhaiWenTan
2026-05-07 21:47 ` [Intel-wired-lan] [PATCH iwl-next v5 1/4] igc: remove unused autoneg_failed field KhaiWenTan
2026-05-07 21:47 ` KhaiWenTan
2026-06-14 7:16 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-06-15 8:22 ` Kwapulinski, Piotr
2026-06-15 8:22 ` Kwapulinski, Piotr
2026-05-07 21:47 ` [Intel-wired-lan] [PATCH iwl-next v5 2/4] igc: move autoneg-enabled settings into igc_handle_autoneg_enabled() KhaiWenTan
2026-05-07 21:47 ` KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-05-07 21:47 ` [Intel-wired-lan] [PATCH iwl-next v5 3/4] igc: replace goto out with direct returns in igc_config_fc_after_link_up() KhaiWenTan
2026-05-07 21:47 ` KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-05-07 21:47 ` [Intel-wired-lan] [PATCH iwl-next v5 4/4] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-05-07 21:47 ` KhaiWenTan
2026-06-14 7:17 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-05-11 16:28 ` Simon Horman [this message]
2026-05-11 16:28 ` [Intel-wired-lan] [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=20260511162809.GF27589@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.