[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172469043299.64426.5670112366033990783.git-patchwork-notify@kernel.org>
Date: Mon, 26 Aug 2024 16:40:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: andrew@...n.ch, hkallweit1@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, corbet@....net,
kernel@...gutronix.de, linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux@...linux.org.uk
Subject: Re: [PATCH net-next v3 0/3] Add ALCD Support to Cable Testing Interface
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 22 Aug 2024 14:07:00 +0200 you wrote:
> Hi all,
>
> This patch series introduces support for Active Link Cable Diagnostics
> (ALCD) in the ethtool cable testing interface and the DP83TD510 PHY
> driver.
>
> Why ALCD?
> On a 10BaseT1L interface, TDR (Time Domain Reflectometry) is not
> possible if the link partner is active - TDR will fail in these cases
> because it requires interrupting the link. Since the link is active, we
> already know the cable is functioning, so instead of using TDR, we can
> use ALCD.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] ethtool: Extend cable testing interface with result source information
https://git.kernel.org/netdev/net-next/c/abcd3026dd63
- [net-next,v3,2/3] ethtool: Add support for specifying information source in cable test results
https://git.kernel.org/netdev/net-next/c/4715d87e11ac
- [net-next,v3,3/3] phy: dp83td510: Utilize ALCD for cable length measurement when link is active
https://git.kernel.org/netdev/net-next/c/986a7fa4b454
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists