From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, linux@armlinux.org.uk, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: rename eee_broken_mode
Date: Tue, 11 Feb 2025 23:30:31 +0000 [thread overview]
Message-ID: <173931663101.32942.3159849337298305658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d7924d4e-49b0-4182-831f-73c558d4425e@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 10 Feb 2025 21:48:42 +0100 you wrote:
> eee_broken_mode is used also if an EEE mode isn't actually broken
> but e.g. not supported by MAC. So rename it.
>
> This is split out from a bigger series that needs more rework.
>
> Heiner Kallweit (2):
> net: phy: rename eee_broken_modes to eee_disabled_modes
> net: phy: rename phy_set_eee_broken to phy_disable_eee_mode
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: phy: rename eee_broken_modes to eee_disabled_modes
https://git.kernel.org/netdev/net-next/c/8eb0d381be31
- [net-next,2/2] net: phy: rename phy_set_eee_broken to phy_disable_eee_mode
https://git.kernel.org/netdev/net-next/c/5e7a74b6a357
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-11 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 20:48 [PATCH net-next 0/2] net: phy: rename eee_broken_mode Heiner Kallweit
2025-02-10 20:49 ` [PATCH net-next 1/2] net: phy: rename eee_broken_modes to eee_disabled_modes Heiner Kallweit
2025-02-11 14:05 ` Andrew Lunn
2025-02-10 20:50 ` [PATCH net-next 2/2] net: phy: rename phy_set_eee_broken to phy_disable_eee_mode Heiner Kallweit
2025-02-11 14:05 ` Andrew Lunn
2025-02-11 23:30 ` patchwork-bot+netdevbpf [this message]
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=173931663101.32942.3159849337298305658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.