[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7a05e5c0432f2822b4ef2756b23d3f76@dev.tdt.de>
Date: Fri, 07 Jun 2024 14:12:24 +0200
From: Martin Schiller <ms@....tdt.de>
To: Vladimir Oltean <olteanv@...il.com>
Cc: martin.blumenstingl@...glemail.com, hauke@...ke-m.de, andrew@...n.ch,
f.fainelli@...il.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 04/13] net: dsa: lantiq_gswip: Don't manually
call gswip_port_enable()
On 2024-06-07 13:11, Vladimir Oltean wrote:
> On Thu, Jun 06, 2024 at 10:52:25AM +0200, Martin Schiller wrote:
>> From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
>>
>> We don't need to manually call gswip_port_enable() from within
>> gswip_setup() for the CPU port. DSA does this automatically for us.
>>
>> Signed-off-by: Martin Blumenstingl
>> <martin.blumenstingl@...glemail.com>
>> ---
>
> Not to mention the first thing in gswip_port_enable(), which is:
>
> if (!dsa_is_user_port(ds, port))
> return 0;
>
> So the call is dead code anyway.
As you will have noticed, this code will be brought back to life in the
next
patch.
Powered by blists - more mailing lists