[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06f101dc957c$c3cd5790$4b6806b0$@trustnetic.com>
Date: Wed, 4 Feb 2026 10:20:00 +0800
From: Jiawen Wu <jiawenwu@...stnetic.com>
To: "'Andrew Lunn'" <andrew@...n.ch>
Cc: <netdev@...r.kernel.org>,
"'Andrew Lunn'" <andrew+netdev@...n.ch>,
"'David S. Miller'" <davem@...emloft.net>,
"'Eric Dumazet'" <edumazet@...gle.com>,
"'Jakub Kicinski'" <kuba@...nel.org>,
"'Paolo Abeni'" <pabeni@...hat.com>,
"'Simon Horman'" <horms@...nel.org>,
"'Mengyuan Lou'" <mengyuanlou@...-swift.com>,
<netdev@...r.kernel.org>,
"'Andrew Lunn'" <andrew+netdev@...n.ch>,
"'David S. Miller'" <davem@...emloft.net>,
"'Eric Dumazet'" <edumazet@...gle.com>,
"'Jakub Kicinski'" <kuba@...nel.org>,
"'Paolo Abeni'" <pabeni@...hat.com>,
"'Simon Horman'" <horms@...nel.org>,
"'Mengyuan Lou'" <mengyuanlou@...-swift.com>
Subject: RE: [PATCH net-next v1 2/7] net: ngbe: improve the reset flow
On Tue, Feb 3, 2026 9:56 PM, Andrew Lunn wrote:
> > static void ngbe_reset(struct wx *wx)
> > {
> > + int err;
> > +
> > + err = ngbe_reset_hw(wx);
> > + if (err != 0)
>
> The != 0 is a bit odd. It looks like rest of the driver uses if (err)
>
> > + wx_err(wx, "Hardware Error: %d\n", err);
>
> I also wounder if this should be fatal? Should ngbe_reset() be made an
> int function so the error code can be returned?
The error returned by ngbe_reset_hw() indicates that there is a hardware
issue, and the recovery process will be handled in another work queue.
We hope that the driver can continue to complete the remaining software
reset.
Powered by blists - more mailing lists