From: Heiner Kallweit <hkallweit1@gmail.com>
To: Suman Ghosh <sumang@marvell.com>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [EXTERNAL] [PATCH net-next] r8169: switch to new function phy_support_eee
Date: Fri, 8 Mar 2024 08:48:38 +0100 [thread overview]
Message-ID: <d6ee6353-5cb0-4751-9b69-255ab62e6b56@gmail.com> (raw)
In-Reply-To: <SJ0PR18MB52166D474EE78BC4E7B6B3E9DB272@SJ0PR18MB5216.namprd18.prod.outlook.com>
On 08.03.2024 08:37, Suman Ghosh wrote:
> Hi Heiner,
>
> To me it looks like both patches,
> r8169: switch to new function phy_support_eee and net: phy: simplify a check in phy_check_link_status is related and can be pushed as a series. This will make change more harmonic. Because, you are moving setting of enable_tx_lpi in one patch and removing from the other one.
>
Both patches are unrelated. The phylib change is just a minor cleanup
w/o functional change.
> Regards,
> Suman
>
>> -----Original Message-----
>> From: Heiner Kallweit <hkallweit1@gmail.com>
>> Sent: Friday, March 8, 2024 2:53 AM
>> To: Realtek linux nic maintainers <nic_swsd@realtek.com>; Paolo Abeni
>> <pabeni@redhat.com>; Jakub Kicinski <kuba@kernel.org>; David Miller
>> <davem@davemloft.net>; Eric Dumazet <edumazet@google.com>
>> Cc: netdev@vger.kernel.org
>> Subject: [EXTERNAL] [PATCH net-next] r8169: switch to new function
>> phy_support_eee
>> Switch to new function phy_support_eee. This allows to simplify the code
>> because data->tx_lpi_enabled is now populated by phy_ethtool_get_eee().
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/net/ethernet/realtek/r8169_main.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/realtek/r8169_main.c
>> b/drivers/net/ethernet/realtek/r8169_main.c
>> index 0d2cbb32c..5c879a5c8 100644
>> --- a/drivers/net/ethernet/realtek/r8169_main.c
>> +++ b/drivers/net/ethernet/realtek/r8169_main.c
>> @@ -2079,7 +2079,6 @@ static int rtl8169_get_eee(struct net_device *dev,
>> struct ethtool_keee *data)
>> return ret;
>>
>> data->tx_lpi_timer = r8169_get_tx_lpi_timer_us(tp);
>> - data->tx_lpi_enabled = data->tx_lpi_timer ? data->eee_enabled :
>> false;
>>
>> return 0;
>> }
>> @@ -5174,7 +5173,7 @@ static int r8169_mdio_register(struct
>> rtl8169_private *tp)
>>
>> tp->phydev->mac_managed_pm = true;
>> if (rtl_supports_eee(tp))
>> - phy_advertise_eee_all(tp->phydev);
>> + phy_support_eee(tp->phydev);
>> phy_support_asym_pause(tp->phydev);
>>
>> /* PHY will be woken up in rtl_open() */
>> --
>> 2.44.0
>>
>
next prev parent reply other threads:[~2024-03-08 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 21:23 [PATCH net-next] r8169: switch to new function phy_support_eee Heiner Kallweit
2024-03-08 7:37 ` [EXTERNAL] " Suman Ghosh
2024-03-08 7:48 ` Heiner Kallweit [this message]
2024-03-11 21:10 ` patchwork-bot+netdevbpf
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=d6ee6353-5cb0-4751-9b69-255ab62e6b56@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=sumang@marvell.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).