From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Sergei Antonov <saproj@gmail.com>, netdev@vger.kernel.org
Subject: Re: Regression: supported_interfaces filling enforcement
Date: Thu, 13 Jul 2023 16:08:31 +0100 [thread overview]
Message-ID: <ZLATb/obklRDT3KW@shell.armlinux.org.uk> (raw)
In-Reply-To: <20230710123556.gufuowtkre652fdp@skbuf>
On Mon, Jul 10, 2023 at 03:35:56PM +0300, Vladimir Oltean wrote:
> On Tue, Jul 04, 2023 at 05:28:47PM +0300, Sergei Antonov wrote:
> > Hello!
> > This commit seems to break the mv88e6060 dsa driver:
> > de5c9bf40c4582729f64f66d9cf4920d50beb897 "net: phylink: require
> > supported_interfaces to be filled"
> >
> > The driver does not fill 'supported_interfaces'. What is the proper
> > way to fix it? I managed to fix it by the following quick code.
> > Comments? Recommendations?
>
> Ok, it seems that commit de5c9bf40c45 ("net: phylink: require
> supported_interfaces to be filled") was based on a miscalculation.
Yes, it seems so. I'm not great with dealing with legacy stuff - which
is something I've stated time and time again when drivers fall behind
with phylink development. There's only so much that I can hold in my
head, and I can't runtime test the legacy stuff.
I suspect two other DSA drivers are also broken by this:
drivers/net/dsa/dsa_loop.c
drivers/net/dsa/realtek/rtl8366rb.c
based upon:
$ grep -lr dsa_switch_ops drivers/net/dsa | xargs grep -L '\.phylink_get_caps.*=' | xargs grep -L '\.adjust_link'
--
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-13 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 14:28 Regression: supported_interfaces filling enforcement Sergei Antonov
2023-07-08 14:01 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-30 16:16 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-07-10 12:35 ` Vladimir Oltean
2023-07-10 14:35 ` Sergei Antonov
2023-07-10 15:38 ` Vladimir Oltean
2023-07-10 18:09 ` Sergei Antonov
2023-07-11 21:58 ` Vladimir Oltean
2023-07-12 0:58 ` Andrew Lunn
2023-08-09 12:11 ` Russell King (Oracle)
2023-07-13 15:08 ` Russell King (Oracle) [this message]
2023-07-25 10:58 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-25 11:26 ` Russell King (Oracle)
2023-07-26 13:45 ` Vladimir Oltean
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=ZLATb/obklRDT3KW@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=saproj@gmail.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).