[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <95ca2bceeb4326b993a160f5c4e8b060e4f47392.camel@microchip.com>
Date: Fri, 10 Mar 2023 04:22:34 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <olteanv@...il.com>, <andrew@...n.ch>, <f.fainelli@...il.com>,
<kuba@...nel.org>, <pabeni@...hat.com>, <edumazet@...gle.com>,
<o.rempel@...gutronix.de>, <Woojung.Huh@...rochip.com>,
<davem@...emloft.net>
CC: <linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>, <kernel@...gutronix.de>
Subject: Re: [PATCH net-next v2 1/2] net: dsa: microchip: add
ksz_setup_tc_mode() function
On Fri, 2023-03-10 at 04:00 +0000, Arun Ramadoss - I17769 wrote:
> On Wed, 2023-03-08 at 10:12 +0100, Oleksij Rempel wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > know the content is safe
> >
> > Add ksz_setup_tc_mode() to make queue scheduling and shaping
> > configuration more visible.
> >
> > Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
>
> Acked-by: Arun Ramadoss <arun.ramadoss@...rochip.com
>
If the ets command is supported only in KSZ9477 series of switch, do we
need to return Not supported for KSZ87xx/KSZ88xx switch similar to tc
cbs implementation. I could infer from the patch set that, all the
register set are for KSZ9477, so invoking the command in
KSZ87xx/KSZ88xx will have undefined behaviour. Correct me if I am
wrong.
Powered by blists - more mailing lists