From: Simon Horman <horms@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Anthony Nguyen <anthony.l.nguyen@intel.com>,
Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
vgrinber@redhat.com, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-net 2/2] ice: don't leave device non-functional if Tx scheduler config fails
Date: Fri, 18 Jul 2025 21:08:55 +0100 [thread overview]
Message-ID: <20250718200855.GN2459@horms.kernel.org> (raw)
In-Reply-To: <95ddc646-d348-45e3-b1f8-b0f114163b11@intel.com>
On Fri, Jul 18, 2025 at 12:56:29PM -0700, Jacob Keller wrote:
>
>
> On 7/18/2025 9:50 AM, Simon Horman wrote:
> > On Thu, Jul 17, 2025 at 09:57:09AM -0700, Jacob Keller wrote:
> >>
> >> Fixes: 91427e6d9030 ("ice: Support 5 layer topology")
> >> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> >
> > Thanks for the extensive explanation.
> >
>
> Thanks. This took me forever to track down exactly what went wrong,
> enough that I had to have the customer send me the card back because we
> thought the firmware was unrecoverable and bricked.
Ouch!
...
> >> msleep(1000);
> >> ice_reset(hw, ICE_RESET_CORER);
> >> - /* CORER will clear the global lock, so no explicit call
> >> - * required for release.
> >> - */
> >> + ice_check_reset(hw);
> >>
> >> - return 0;
> >> +reinit_hw:
> >
> > nit: I think you can move this label above ice_check_reset().
> > As the only place that jumps to this label calls ice_check_reset()
> > immediately before doing so. If so, renaming the label might
> > also be appropriate (up to you on all fronts:)
> >
>
> You're right thats probably slightly better. I'm not sure its worth a
> re-roll vs getting this fix out since its a pretty minor difference.
Yes, agreed. I'm happy to let this lie if you prefer.
...
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Anthony Nguyen <anthony.l.nguyen@intel.com>,
Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
vgrinber@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-net 2/2] ice: don't leave device non-functional if Tx scheduler config fails
Date: Fri, 18 Jul 2025 21:08:55 +0100 [thread overview]
Message-ID: <20250718200855.GN2459@horms.kernel.org> (raw)
In-Reply-To: <95ddc646-d348-45e3-b1f8-b0f114163b11@intel.com>
On Fri, Jul 18, 2025 at 12:56:29PM -0700, Jacob Keller wrote:
>
>
> On 7/18/2025 9:50 AM, Simon Horman wrote:
> > On Thu, Jul 17, 2025 at 09:57:09AM -0700, Jacob Keller wrote:
> >>
> >> Fixes: 91427e6d9030 ("ice: Support 5 layer topology")
> >> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> >
> > Thanks for the extensive explanation.
> >
>
> Thanks. This took me forever to track down exactly what went wrong,
> enough that I had to have the customer send me the card back because we
> thought the firmware was unrecoverable and bricked.
Ouch!
...
> >> msleep(1000);
> >> ice_reset(hw, ICE_RESET_CORER);
> >> - /* CORER will clear the global lock, so no explicit call
> >> - * required for release.
> >> - */
> >> + ice_check_reset(hw);
> >>
> >> - return 0;
> >> +reinit_hw:
> >
> > nit: I think you can move this label above ice_check_reset().
> > As the only place that jumps to this label calls ice_check_reset()
> > immediately before doing so. If so, renaming the label might
> > also be appropriate (up to you on all fronts:)
> >
>
> You're right thats probably slightly better. I'm not sure its worth a
> re-roll vs getting this fix out since its a pretty minor difference.
Yes, agreed. I'm happy to let this lie if you prefer.
...
next prev parent reply other threads:[~2025-07-18 20:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 16:57 [Intel-wired-lan] [PATCH iwl-net 0/2] ice: fix issues with loading certain older DDP packages Jacob Keller
2025-07-17 16:57 ` Jacob Keller
2025-07-17 16:57 ` [Intel-wired-lan] [PATCH iwl-net 1/2] ice: fix double-call to ice_deinit_hw() during probe failure Jacob Keller
2025-07-17 16:57 ` Jacob Keller
2025-07-18 16:50 ` [Intel-wired-lan] " Simon Horman
2025-07-18 16:50 ` Simon Horman
2025-07-21 15:00 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-07-21 15:00 ` Loktionov, Aleksandr
2025-08-18 10:27 ` [Intel-wired-lan] " Przemek Kitszel
2025-08-18 10:27 ` Przemek Kitszel
2025-08-18 22:38 ` [Intel-wired-lan] " Jacob Keller
2025-08-18 22:38 ` Jacob Keller
2025-08-18 16:21 ` [Intel-wired-lan] " Rinitha, SX
2025-08-18 16:21 ` Rinitha, SX
2025-07-17 16:57 ` [Intel-wired-lan] [PATCH iwl-net 2/2] ice: don't leave device non-functional if Tx scheduler config fails Jacob Keller
2025-07-17 16:57 ` Jacob Keller
2025-07-18 16:50 ` [Intel-wired-lan] " Simon Horman
2025-07-18 16:50 ` Simon Horman
2025-07-18 19:56 ` [Intel-wired-lan] " Jacob Keller
2025-07-18 19:56 ` Jacob Keller
2025-07-18 20:08 ` Simon Horman [this message]
2025-07-18 20:08 ` Simon Horman
2025-08-18 16:21 ` [Intel-wired-lan] " Rinitha, SX
2025-08-18 16:21 ` Rinitha, SX
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=20250718200855.GN2459@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=jacob.e.keller@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vgrinber@redhat.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.