From: Paolo Abeni <pabeni@redhat.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
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>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH net-next v2 2/4] net: phy: c45: add genphy_c45_an_config_eee_aneg() function
Date: Tue, 21 Feb 2023 12:57:29 +0100 [thread overview]
Message-ID: <89c3f9b68d8030270ad58af2d9c94ae43eb5b1e6.camel@redhat.com> (raw)
In-Reply-To: <20230221050334.578012-3-o.rempel@pengutronix.de>
On Tue, 2023-02-21 at 06:03 +0100, Oleksij Rempel wrote:
> Add new genphy_c45_an_config_eee_aneg() function and replace some of
> genphy_c45_write_eee_adv() calls. This will be needed by the next patch.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> ---
> drivers/net/phy/phy-c45.c | 12 +++++++++++-
> drivers/net/phy/phy_device.c | 2 +-
> include/linux/phy.h | 1 +
> 3 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/phy/phy-c45.c b/drivers/net/phy/phy-c45.c
> index f23cce2c5199..904f64818922 100644
> --- a/drivers/net/phy/phy-c45.c
> +++ b/drivers/net/phy/phy-c45.c
> @@ -262,7 +262,7 @@ int genphy_c45_an_config_aneg(struct phy_device *phydev)
> linkmode_and(phydev->advertising, phydev->advertising,
> phydev->supported);
>
> - ret = genphy_c45_write_eee_adv(phydev, phydev->supported_eee);
> + ret = genphy_c45_an_config_eee_aneg(phydev);
> if (ret < 0)
> return ret;
> else if (ret)
> @@ -858,6 +858,16 @@ int genphy_c45_read_eee_abilities(struct phy_device *phydev)
> }
> EXPORT_SYMBOL_GPL(genphy_c45_read_eee_abilities);
>
> +/**
> + * genphy_c45_an_config_eee_aneg - write advertised EEE link modes
> + * @phydev: target phy_device struct
> + * @adv: the linkmode advertisement settings
This function does not have a second argument.
Cheers,
Paolo
next prev parent reply other threads:[~2023-02-21 12:23 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 [this message]
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
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=89c3f9b68d8030270ad58af2d9c94ae43eb5b1e6.camel@redhat.com \
--to=pabeni@redhat.com \
--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=o.rempel@pengutronix.de \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®