From: Vladimir Oltean <olteanv@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v1 3/3] net: dsa: microchip: Fix PHY loopback configuration for KSZ8794 and KSZ8873
Date: Wed, 6 Dec 2023 18:43:29 +0200 [thread overview]
Message-ID: <20231206164329.fszkmpilktyq6r6v@skbuf> (raw)
In-Reply-To: <20231206155440.GA1324895@pengutronix.de>
On Wed, Dec 06, 2023 at 04:54:40PM +0100, Oleksij Rempel wrote:
> > I don't see DSA implementing ndo_set_features(), nor offering NETIF_F_LOOPBACK.
> > The PHY is integrated, so DSA is the only relevant netdev driver. Is
> > there any other way to test this functionality?
>
> yes - net_selftest()
Ok, I didn't notice net_test_phy_loopback_enable(). So it can be
triggered after all, it seems.
But I mean, if it's exclusively a selftest that fails, and has always
failed since its introduction, I think it can be considered new
development work when it stops failing? I don't believe that the impact
of the bug is relevant for users. It's not a production functionality.
Documentation/process/stable-kernel-rules.rst doesn't specifically say
this, but it does imply that we should triage the "real bugs that bother
people" as much as possible.
> > If not, I think it's a case of "tree falling in the woods and nobody
> > hearing it". Not "stable" material. But it definitely has nothing to do
> > with not caring about the switch variant.
>
> Sorry, my intention is not to criticize anyone. I am not getting
> feedbacks or bug reports for ksz88xx variants, so it seems like not many
> people use it in upstream.
>
> When I have time slots to work on this driver, I try to use them to do
> fixes and also clean up the code. Since there is some sort of fog of
> uncertainty about when I get the next time slot, or even if I get it at
> all, I am trying to push both fixes and cleanups together.
>
> But, you are right, it is not a good reason for not caring about stable :)
>
> What is the decision about this patch set?
I wouldn't bend over backwards for this, and reorder the patches.
I would spend my time doing more meaningful things.
next prev parent reply other threads:[~2023-12-06 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 15:24 [PATCH net-next v1 1/3] net: dsa: microchip: ksz8: move BMCR specific code to separate function Oleksij Rempel
2023-11-21 15:24 ` [PATCH net-next v1 2/3] net: dsa: microchip: Remove redundant optimization in ksz8_w_phy_bmcr Oleksij Rempel
2023-11-23 10:54 ` Paolo Abeni
2023-12-06 22:37 ` Vladimir Oltean
2023-11-21 15:24 ` [PATCH net-next v1 3/3] net: dsa: microchip: Fix PHY loopback configuration for KSZ8794 and KSZ8873 Oleksij Rempel
2023-11-23 10:52 ` Paolo Abeni
2023-12-06 8:55 ` Oleksij Rempel
2023-12-06 15:14 ` Vladimir Oltean
2023-12-06 15:54 ` Oleksij Rempel
2023-12-06 16:43 ` Vladimir Oltean [this message]
2023-12-07 0:28 ` Vladimir Oltean
2023-12-07 5:15 ` Oleksij Rempel
2023-12-07 14:00 ` Vladimir Oltean
2023-12-20 9:46 ` Oleksij Rempel
2023-12-06 16:46 ` [PATCH net-next v1 1/3] net: dsa: microchip: ksz8: move BMCR specific code to separate function Vladimir Oltean
2023-12-07 4:57 ` Arun.Ramadoss
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=20231206164329.fszkmpilktyq6r6v@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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