[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250425171703.0a6be54e@kernel.org>
Date: Fri, 25 Apr 2025 17:17:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stefan Wahren <wahrenst@....net>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
netdev@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net 1/5] net: vertexcom: mse102x: Fix possible stuck of
SPI interrupt
On Fri, 25 Apr 2025 09:35:04 +0200 Stefan Wahren wrote:
> Since the SPI implementation on the MSE102x MCU is in software, it
> cannot reply to SPI commands in busy state. So drop the scaring
> statistics about "invalid" command replies.
>
> https://github.com/chargebyte/linux/commit/9f8a69e5c0d6c4482e89d7b86f72069b89a94547
>
> Should I add it as a fix?
I see. I don't think we have to add that to the fixes series.
Worst case if people complain we can request a backport later.
Powered by blists - more mailing lists