From: Simon Horman <horms@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: aleksandr.loktionov@intel.com, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH iwl-next] ice: do not carry link status over to link event data
Date: Sat, 21 Mar 2026 09:18:57 +0000 [thread overview]
Message-ID: <20260321091857.GU74886@horms.kernel.org> (raw)
In-Reply-To: <c1731a39-bcb1-408a-9630-f8878c270d05@intel.com>
On Fri, Mar 20, 2026 at 03:05:24PM -0700, Tony Nguyen wrote:
>
>
> On 3/20/2026 12:33 PM, Simon Horman wrote:
> > 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
> > ---
> > ice: do not carry link status over to link event data
> >
> > This patch removes code that updated the link_up parameter with the
> > current firmware state after calling ice_update_link_info().
> >
> > > diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
> > > index e7308e381e2f..348c86b7328d 100644
> > > --- a/drivers/net/ethernet/intel/ice/ice_main.c
> > > +++ b/drivers/net/ethernet/intel/ice/ice_main.c
> > > @@ -1127,12 +1127,6 @@ ice_link_event(struct ice_pf *pf, struct ice_port_info *pi, bool link_up,
> > >
> > > ice_check_link_cfg_err(pf, pi->phy.link_info.link_cfg_err);
> > >
> > > - /* Check if the link state is up after updating link info, and treat
> > > - * this event as an UP event since the link is actually UP now.
> > > - */
> > > - if (phy_info->link_info.link_info & ICE_AQ_LINK_UP)
> > > - link_up = true;
> > > -
> >
> > Could removing this check create a race condition with stale link events?
>
> This was a part of other changes that allows this to happen. By itself, as
> evidenced here, it does not.
Thanks for the clarification, much appreciated.
prev parent reply other threads:[~2026-03-21 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 5:05 [PATCH iwl-next] ice: do not carry link status over to link event data Aleksandr Loktionov
2026-03-20 19:33 ` Simon Horman
2026-03-20 22:05 ` Tony Nguyen
2026-03-21 9:18 ` Simon Horman [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=20260321091857.GU74886@horms.kernel.org \
--to=horms@kernel.org \
--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