From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] net: phy: EEE fixes
Date: Tue, 21 Feb 2023 10:48:09 +0100 [thread overview]
Message-ID: <20230221094809.GF19238@pengutronix.de> (raw)
In-Reply-To: <Y/SQo20Qes2GpoeM@shell.armlinux.org.uk>
On Tue, Feb 21, 2023 at 09:36:35AM +0000, Russell King (Oracle) wrote:
> On Tue, Feb 21, 2023 at 06:03:30AM +0100, Oleksij Rempel wrote:
> > changes v2:
> > - restore previous ethtool set logic for the case where advertisements
> > are not provided by user space.
>
> I don't think the _kernel_ should be doing this - this introduces a
> different behaviour to the kernel. As I already said, setting the
> default advertisement in the case of ethtool -s is done by userspace
> not by the kernel.
>
> In fact, the kernel explicitly rejects an attempt to have autoneg
> enabled with a zero advertising mask:
>
> linkmode_copy(advertising, cmd->link_modes.advertising);
> linkmode_and(advertising, advertising, phydev->supported);
> if (autoneg == AUTONEG_ENABLE && linkmode_empty(advertising))
> return -EINVAL;
>
> and I think we should have a uniform behaviour with the same API,
> rather than different behaviours, as that becomes quite messy.
I decided to revert this part to not mix different issue. This logic
existed before my refactoring. So, it is better to handle it as
different patch. Current patch set should address only regressions.
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-02-21 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 5:03 [PATCH net-next v2 0/4] net: phy: EEE fixes Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 1/4] net: phy: c45: use "supported_eee" instead of supported for access validation Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 2/4] net: phy: c45: add genphy_c45_an_config_eee_aneg() function Oleksij Rempel
2023-02-21 11:57 ` Paolo Abeni
2023-02-21 5:03 ` [PATCH net-next v2 3/4] net: phy: do not force EEE support Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 4/4] net: phy: c45: genphy_c45_ethtool_set_eee: validate EEE link modes Oleksij Rempel
2023-02-21 9:36 ` [PATCH net-next v2 0/4] net: phy: EEE fixes Russell King (Oracle)
2023-02-21 9:48 ` Oleksij Rempel [this message]
2023-02-21 9:52 ` Russell King (Oracle)
2023-02-21 11:45 ` Paolo Abeni
2023-02-21 11:52 ` Paolo Abeni
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=20230221094809.GF19238@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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).