From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 2/3] net: dsa: allow DSA switch drivers to provide their own phylink mac ops
Date: Tue, 9 Apr 2024 17:29:23 +0100 [thread overview]
Message-ID: <ZhVs41dODkA/B7JH@shell.armlinux.org.uk> (raw)
In-Reply-To: <20240409153346.atvof7b6ziaf2xr5@skbuf>
On Tue, Apr 09, 2024 at 06:33:46PM +0300, Vladimir Oltean wrote:
> On Tue, Apr 09, 2024 at 03:37:31PM +0300, Vladimir Oltean wrote:
> > On Mon, Apr 08, 2024 at 12:19:25PM +0100, Russell King (Oracle) wrote:
> > > +static void dsa_shared_port_link_down(struct dsa_port *dp)
> > > +{
> > > + struct dsa_switch *ds = dp->ds;
> > > +
> > > + if (ds->phylink_mac_ops) {
> > > + if (ds->phylink_mac_ops->mac_link_down)
> > > + ds->phylink_mac_ops->mac_link_down(&dp->pl_config,
> > > + MLO_AN_FIXED,
> > > + PHY_INTERFACE_MODE_NA);
> > > + } else {
> > > + if (ds->ops->phylink_mac_link_down)
> > > + ds->ops->phylink_mac_link_down(ds, dp->index,
> > > + MLO_AN_FIXED, PHY_INTERFACE_MODE_NA);
> > > + }
> > > +}
> >
> > Please roll this other change into the patch when respinning:
> >
> > else {
> > if { }
> > }
> >
> > becomes
> >
> > else if {}
This would destroy the symmetry that I think aids readability. I did
consider it at the time and decided against it.
> Something like this:
>
> static void dsa_shared_port_link_down(struct dsa_port *dp)
> {
> struct dsa_switch *ds = dp->ds;
>
> if (ds->phylink_mac_ops && ds->phylink_mac_ops->mac_link_down) {
> ds->phylink_mac_ops->mac_link_down(&dp->pl_config, MLO_AN_FIXED,
> PHY_INTERFACE_MODE_NA);
> } else if (ds->ops->phylink_mac_link_down) {
> ds->ops->phylink_mac_link_down(ds, dp->index, MLO_AN_FIXED,
> PHY_INTERFACE_MODE_NA);
> }
This changes the logic - it allows driver authors to provide the
MAC operations, omit the mac_link_down() op _and_ an
ops->phylink_mac_link_down() function. This could lead to buggy
drivers since this will only happen in this path and none of the
others.
I want this to be an "either provide phylink_mac_ops, and thus
none of the phylink_mac_* ops in dsa_switch_ops will be called" or
"don't provide phylink_mac_ops and the phylink_mac_* ops in
dsa_switch_ops will be called". It's then completely clear cut
that it's one or the other, whereas the code above makes it
unclear.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-04-09 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 11:19 [PATCH net-next 0/3] net: dsa: allow phylink_mac_ops in DSA drivers Russell King (Oracle)
2024-04-08 11:19 ` [PATCH net-next 1/3] net: dsa: introduce dsa_phylink_to_port() Russell King (Oracle)
2024-04-08 23:41 ` Andrew Lunn
2024-04-08 23:50 ` Florian Fainelli
2024-04-08 11:19 ` [PATCH net-next 2/3] net: dsa: allow DSA switch drivers to provide their own phylink mac ops Russell King (Oracle)
2024-04-08 23:45 ` Andrew Lunn
2024-04-08 23:51 ` Florian Fainelli
2024-04-09 3:15 ` kernel test robot
2024-04-09 8:04 ` Russell King (Oracle)
2024-04-09 12:37 ` Vladimir Oltean
2024-04-09 15:33 ` Vladimir Oltean
2024-04-09 16:29 ` Russell King (Oracle) [this message]
2024-04-09 16:52 ` Vladimir Oltean
2024-04-09 18:22 ` Russell King (Oracle)
2024-04-08 11:19 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: provide own phylink MAC operations Russell King (Oracle)
2024-04-08 23:45 ` Andrew Lunn
2024-04-08 23:51 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZhVs41dODkA/B7JH@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).