[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5hln5qd5p6mbg2hpmptkhlrjymgwzf3ioufwqbzmtrrfhkgecb@ew57gxpcjgwr>
Date: Fri, 8 Dec 2023 11:06:48 +0000
From: Alvin Šipraga <ALSI@...g-olufsen.dk>
To: Luiz Angelo Daros de Luca <luizluca@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>, "andrew@...n.ch"
<andrew@...n.ch>, "f.fainelli@...il.com" <f.fainelli@...il.com>,
"olteanv@...il.com" <olteanv@...il.com>, "davem@...emloft.net"
<davem@...emloft.net>, "edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>,
"arinc.unal@...nc9.com" <arinc.unal@...nc9.com>
Subject: Re: [PATCH net-next 7/7] net: dsa: realtek: always use the realtek
user mdio driver
On Fri, Dec 08, 2023 at 01:41:43AM -0300, Luiz Angelo Daros de Luca wrote:
> Although the DSA switch will register a generic mdio driver when
> ds_ops.phy_{read,write} exists ("dsa user smi"), it was pointed out that
> it was not a core feature to depend on [1]. That way, the realtek user
> mdio driver will be used by both interfaces.
>
> [1] https://lkml.kernel.org/netdev/20220630200423.tieprdu5fpabflj7@bang-olufsen.dk/T/
>
> The ds_ops field in realtek_priv was also dropped as now we can directly
> reference the variant->ds_ops.
Ah OK, this makes more sense. Can you fold this into the previous patch?
Then it might look more reasonable.
Powered by blists - more mailing lists