From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <anthony.l.nguyen@intel.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: add ethtool reset support to safe mode ops
Date: Tue, 17 Mar 2026 15:11:18 +0100 [thread overview]
Message-ID: <91d29df8-ebc1-4d9d-9d1f-022aafdc3e72@intel.com> (raw)
In-Reply-To: <20260317084459.2196606-1-aleksandr.loktionov@intel.com>
On 3/17/26 09:44, Aleksandr Loktionov wrote:
> From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
>
> Wire up ice_ethtool_reset() into ice_ethtool_safe_mode_ops so that the
> .reset ethtool operation is available when the driver is operating in safe
> mode, consistent with the behaviour exposed by the full ice_ethtool_ops.
>
> Without this, a user-space call to ethtool --reset while the driver is in
> safe mode would return EOPNOTSUPP even though the underlying reset logic
> is fully implemented and works correctly.
>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_ethtool.c b/drivers/net/ethernet/intel/ice/ice_ethtool.c
> index 301947d..bf90bd5 100644
> --- a/drivers/net/ethernet/intel/ice/ice_ethtool.c
> +++ b/drivers/net/ethernet/intel/ice/ice_ethtool.c
> @@ -4917,6 +4917,7 @@ static const struct ethtool_ops ice_ethtool_safe_mode_ops = {
> .set_ringparam = ice_set_ringparam,
> .nway_reset = ice_nway_reset,
> .get_channels = ice_get_channels,
> + .reset = ice_ethtool_reset,
> };
>
> /**
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
prev parent reply other threads:[~2026-03-17 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 8:44 [PATCH iwl-next v1] ice: add ethtool reset support to safe mode ops Aleksandr Loktionov
2026-03-17 14:11 ` Przemek Kitszel [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=91d29df8-ebc1-4d9d-9d1f-022aafdc3e72@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
/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