From: patchwork-bot+netdevbpf@kernel.org
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v10 0/5] Support loopback mode speed selection
Date: Thu, 20 Mar 2025 07:50:35 +0000 [thread overview]
Message-ID: <174245703551.1336672.1445153240508578190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312203010.47429-1-gerhard@engleder-embedded.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 12 Mar 2025 21:30:05 +0100 you wrote:
> Previously to commit 6ff3cddc365b ("net: phylib: do not disable autoneg
> for fixed speeds >= 1G") it was possible to select the speed of the
> loopback mode by configuring a fixed speed before enabling the loopback
> mode. Now autoneg is always enabled for >= 1G and a fixed speed of >= 1G
> requires successful autoneg. Thus, the speed of the loopback mode depends
> on the link partner for >= 1G. There is no technical reason to depend on
> the link partner for loopback mode. With this behavior the loopback mode
> is less useful for testing.
>
> [...]
Here is the summary with links:
- [net-next,v10,1/5] net: phy: Allow loopback speed selection for PHY drivers
https://git.kernel.org/netdev/net-next/c/45456e38c44e
- [net-next,v10,2/5] net: phy: Support speed selection for PHY loopback
https://git.kernel.org/netdev/net-next/c/0d60fd50328a
- [net-next,v10,3/5] net: phy: micrel: Add loopback support
https://git.kernel.org/netdev/net-next/c/fe4bf60ffdff
- [net-next,v10,4/5] net: phy: marvell: Align set_loopback() implementation
https://git.kernel.org/netdev/net-next/c/1a0df6c96ce5
- [net-next,v10,5/5] tsnep: Select speed for loopback
https://git.kernel.org/netdev/net-next/c/163d744d020e
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-03-20 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 20:30 [PATCH net-next v10 0/5] Support loopback mode speed selection Gerhard Engleder
2025-03-12 20:30 ` [PATCH net-next v10 1/5] net: phy: Allow loopback speed selection for PHY drivers Gerhard Engleder
2025-03-12 20:30 ` [PATCH net-next v10 2/5] net: phy: Support speed selection for PHY loopback Gerhard Engleder
2025-03-12 20:30 ` [PATCH net-next v10 3/5] net: phy: micrel: Add loopback support Gerhard Engleder
2025-03-13 8:57 ` Maxime Chevallier
2025-03-13 9:35 ` Gerhard Engleder
2025-03-13 9:41 ` Maxime Chevallier
2025-03-12 20:30 ` [PATCH net-next v10 4/5] net: phy: marvell: Align set_loopback() implementation Gerhard Engleder
2025-03-12 20:30 ` [PATCH net-next v10 5/5] tsnep: Select speed for loopback Gerhard Engleder
2025-03-20 6:26 ` [PATCH net-next v10 0/5] Support loopback mode speed selection Gerhard Engleder
2025-03-20 7:32 ` Paolo Abeni
2025-03-20 7:50 ` 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=174245703551.1336672.1445153240508578190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox