public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: tony@atomide.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux@armlinux.org.uk, andrew@lunn.ch,
	andrew+netdev@lunn.ch, pabeni@redhat.com, kuba@kernel.org,
	davem@davemloft.net, edumazet@google.com, horms@kernel.org,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: add and use phy_disable_eee
Date: Fri, 20 Dec 2024 03:30:36 +0000	[thread overview]
Message-ID: <173466543676.2462446.11795736705448322037.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5139374e-7151-4d0d-8ba9-9ec3d9b52f67@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 16 Dec 2024 22:29:58 +0100 you wrote:
> If a MAC driver doesn't support EEE, then the PHY shouldn't advertise it.
> Add phy_disable_eee() for this purpose, and use it in cpsw driver.
> 
> Heiner Kallweit (3):
>   net: phy: add phy_disable_eee
>   net: ethernet: ti: cpsw: disable PHY EEE advertisement
>   ARM: dts: ti/omap: remove eee-broken properties
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] net: phy: add phy_disable_eee
    https://git.kernel.org/netdev/net-next/c/b55498ff14bd
  - [net-next,2/3] net: ethernet: ti: cpsw: disable PHY EEE advertisement
    https://git.kernel.org/netdev/net-next/c/c9f5a5dabbf5
  - [net-next,3/3] ARM: dts: ti/omap: remove eee-broken properties
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-12-20  3:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 21:29 [PATCH net-next 0/3] net: add and use phy_disable_eee Heiner Kallweit
2024-12-16 21:31 ` [PATCH net-next 1/3] net: phy: add phy_disable_eee Heiner Kallweit
2024-12-17 10:43   ` Andrew Lunn
2024-12-17 20:50     ` Heiner Kallweit
2024-12-17 22:34       ` Andrew Lunn
2024-12-18  7:01         ` Heiner Kallweit
2024-12-19  2:59     ` Jakub Kicinski
2024-12-19  8:41       ` Andrew Lunn
2024-12-19  8:34   ` Andrew Lunn
2024-12-16 21:32 ` [PATCH net-next 2/3] net: ethernet: ti: cpsw: disable PHY EEE advertisement Heiner Kallweit
2024-12-19  8:34   ` Andrew Lunn
2024-12-16 21:33 ` [PATCH net-next 3/3] ARM: dts: ti/omap: remove eee-broken properties Heiner Kallweit
2024-12-19  8:35   ` Andrew Lunn
2024-12-20  3:30 ` patchwork-bot+netdevbpf [this message]
2024-12-20  8:26   ` [PATCH net-next 0/3] net: add and use phy_disable_eee Heiner Kallweit
2024-12-20  8:40     ` Andrew Lunn
2024-12-20 14:25       ` Jakub Kicinski
2024-12-20 22:14         ` Heiner Kallweit

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=173466543676.2462446.11795736705448322037.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=tony@atomide.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