[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b0d42df6b3f2f17f77cfb45cf8339da@kapio-technology.com>
Date: Thu, 08 Dec 2022 13:28:27 +0100
From: netdev@...io-technology.com
To: Vladimir Oltean <olteanv@...il.com>
Cc: Ido Schimmel <idosch@...sch.org>, davem@...emloft.net,
kuba@...nel.org, netdev@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: mac-auth/MAB
implementation
On 2022-12-07 21:29, Vladimir Oltean wrote:
> On Tue, Dec 06, 2022 at 05:36:42PM +0100, netdev@...io-technology.com
> wrote:
>> > I was under the impression that we agreed that the locking change will
>> > be split to a separate patch.
>>
>> Sorry, I guess that because of the quite long time that has passed as
>> I
>> needed to get this FID=0 issue sorted out, and had many other
>> different
>> changes to attend, I forgot.
>
> Well, at least you got the FID=0 issue sorted out... right?
> What was the cause, what is the solution?
Well I got it sorted out in the way that I have identified that it is
the ATU op that fails some times. I don't think there is anything that
can be done about that, other than what I do and let the interrupt
routing return an error.
Powered by blists - more mailing lists