[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7a99b7c7615f20a69afa4a6bf82740cf194738dc.camel@microchip.com>
Date: Mon, 6 Feb 2023 14:38:41 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <olteanv@...il.com>, <Rakesh.Sankaranarayanan@...rochip.com>
CC: <andrew@...n.ch>, <linux-kernel@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>, <linux@...linux.org.uk>,
<f.fainelli@...il.com>, <kuba@...nel.org>, <pabeni@...hat.com>,
<edumazet@...gle.com>, <netdev@...r.kernel.org>,
<Woojung.Huh@...rochip.com>, <davem@...emloft.net>
Subject: Re: [RFC PATCH net-next 04/11] net: dsa: microchip: lan937x: update
port number for LAN9373
Hi Vladimir,
On Sat, 2023-02-04 at 01:26 +0200, Vladimir Oltean wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Fri, Feb 03, 2023 at 10:43:40AM +0000,
> Rakesh.Sankaranarayanan@...rochip.com wrote:
> > Hi Andrew,
> >
> > On Thu, 2023-02-02 at 16:19 +0100, Andrew Lunn wrote:
> > > > LAN9373 have total 8 physical ports. Update port_cnt member in
> > > > ksz_chip_data structure.
> > >
> > > This seems more like a fix. Should it be applied to net, not net-
> > > next,
> > > and have Fixes: tag?
> > >
> > > Andrew
> >
> > Yes, I will update and send it as separate net patch with fixes
> > tag.
>
> What's the story here? Arun must have surely known this isn't a 5
> port switch?
It was my mistake during replicating the structure for LAN9370 and
LAN9373. I tested the basic switch functionality on LAN9370 and LAN9374
but not LAN9373. LAN9373 Evaluation board available in cascading setup.
When Rakesh brought up the board for cascading, he found out there is
bug. I should have double checked all the structure member before
submitting the patch but I overlooked it.
Powered by blists - more mailing lists