From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH net] net: dsa: fix older DSA drivers using phylink - manual merge
Date: Fri, 28 Jul 2023 11:37:25 +0100 [thread overview]
Message-ID: <ZMOaZdDVkN4bq66C@shell.armlinux.org.uk> (raw)
In-Reply-To: <5d240ea8-3fd9-5e43-1bcf-2923bfddee72@tessares.net>
On Fri, Jul 28, 2023 at 12:23:25PM +0200, Matthieu Baerts wrote:
> Hi Russell,
>
> On 26/07/2023 16:45, Russell King (Oracle) wrote:
> > Older DSA drivers that do not provide an dsa_ops adjust_link method end
> > up using phylink. Unfortunately, a recent phylink change that requires
> > its supported_interfaces bitmap to be filled breaks these drivers
> > because the bitmap remains empty.
> >
> > Rather than fixing each driver individually, fix it in the core code so
> > we have a sensible set of defaults.
> >
> > Reported-by: Sergei Antonov <saproj@gmail.com>
> > Fixes: de5c9bf40c45 ("net: phylink: require supported_interfaces to be filled")
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> FYI, we got a small conflict when merging 'net' in 'net-next' in the
> MPTCP tree due to this patch applied in 'net':
>
> 9945c1fb03a3 ("net: dsa: fix older DSA drivers using phylink")
>
> and this one from 'net-next':
>
> a88dd7538461 ("net: dsa: remove legacy_pre_march2020 detection")
It was unavoidable.
> ----- Generic Message -----
> The best is to avoid conflicts between 'net' and 'net-next' trees but if
> they cannot be avoided when preparing patches, a note about how to fix
> them is much appreciated.
Given that this is a trivial context-based conflict, it wasn't worth it.
If it was a conflict that actually involved two changes touching the
same lines of code, then yes, that would be sensible.
Note that I don't get these messages from the netdev maintainers when
they update net-next (as they did last night.)
>
> - if (ds->ops->phylink_get_caps)
> - /* Presence of phylink_mac_link_state or phylink_mac_an_restart is
> - * an indicator of a legacy phylink driver.
> - */
> - if (ds->ops->phylink_mac_link_state ||
> - ds->ops->phylink_mac_an_restart)
> - dp->pl_config.legacy_pre_march2020 = true;
> -
> + if (ds->ops->phylink_get_caps) {
> ds->ops->phylink_get_caps(ds, dp->index, &dp->pl_config);
> + } else {
> + /* For legacy drivers */
> + __set_bit(PHY_INTERFACE_MODE_INTERNAL,
> + dp->pl_config.supported_interfaces);
> + __set_bit(PHY_INTERFACE_MODE_GMII,
> + dp->pl_config.supported_interfaces);
> + }
Of course, being a purely context-based conflict, that is correct.
--
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:[~2023-07-28 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:45 [PATCH net] net: dsa: fix older DSA drivers using phylink Russell King (Oracle)
2023-07-26 16:36 ` Vladimir Oltean
2023-07-26 16:37 ` Florian Fainelli
2023-07-28 0:50 ` patchwork-bot+netdevbpf
2023-07-28 10:23 ` [PATCH net] net: dsa: fix older DSA drivers using phylink - manual merge Matthieu Baerts
2023-07-28 10:37 ` Russell King (Oracle) [this message]
2023-07-28 11:23 ` Matthieu Baerts
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=ZMOaZdDVkN4bq66C@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=matthieu.baerts@tessares.net \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.