[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <383e4a23-447e-4024-8dc9-fc52ea209025@lunn.ch>
Date: Fri, 26 Sep 2025 15:13:59 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Parvathi Pudi <parvathi@...thit.com>
Cc: andrew+netdev <andrew+netdev@...n.ch>, davem <davem@...emloft.net>,
edumazet <edumazet@...gle.com>, kuba <kuba@...nel.org>,
pabeni <pabeni@...hat.com>, danishanwar <danishanwar@...com>,
rogerq <rogerq@...nel.org>, pmohan <pmohan@...thit.com>,
basharath <basharath@...thit.com>, afd <afd@...com>,
linux-kernel <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
pratheesh <pratheesh@...com>, Prajith Jayarajan <prajith@...com>,
Vignesh Raghavendra <vigneshr@...com>, praneeth <praneeth@...com>,
srk <srk@...com>, rogerq <rogerq@...com>,
krishna <krishna@...thit.com>, mohan <mohan@...thit.com>
Subject: Re: [PATCH net-next 0/3] RSTP SWITCH support for PRU-ICSSM Ethernet
driver
> No, this patch-set applies to both STP and RSTP. The driver and firmware
> responds to the port-state transitions and FDB operations through the
> standard Linux switchdev/bridge interfaces, with no STP/RSTP related
> logic executed in driver/firmware.
>
> We referred to RSTP in the commit message as it is our primary use case
> and it implies support for STP as well.
I would not say RSTP implied STP, because the higher level
implementation is very different. You need to know the low level
details to understand they use the same driver API.
Please generalise the commit messages, mention STP as well as RSTP.
Thanks
Andrew
Powered by blists - more mailing lists