[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551b958d6df4ee608a5da6064a2843db@kapio-technology.com>
Date: Tue, 15 Nov 2022 16:14:05 +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 v8 net-next 0/2] mv88e6xxx: Add MAB offload support
On 2022-11-15 15:56, Vladimir Oltean wrote:
> On Tue, Nov 15, 2022 at 02:25:13PM +0100, netdev@...io-technology.com
> wrote:
>> On 2022-11-15 13:22, Vladimir Oltean wrote:
>
>> The bridge_locked_port.sh tests all succeeded... as expected... ;-)
>
> Yeah, I confirm this works on a 6390 over here.
Thanks :-)
> But I still don't like
> the log spam from the IRQ handlers.
>
> [root@mox:~/.../drivers/net/dsa] # ./bridge_locked_port.sh lan1 lan2
> lan3 lan4
> [ 1298.218224] mv88e6085 d0032004.mdio-mii:10 lan1: configuring for
> ...
I think the violation log issue should be handled in a seperate
patch(set)?
Powered by blists - more mailing lists