From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
corbet@lwn.net, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next v3 0/3] Add ALCD Support to Cable Testing Interface
Date: Mon, 26 Aug 2024 16:40:32 +0000 [thread overview]
Message-ID: <172469043299.64426.5670112366033990783.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822120703.1393130-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2024-08-26 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 12:07 [PATCH net-next v3 0/3] Add ALCD Support to Cable Testing Interface Oleksij Rempel
2024-08-22 12:07 ` [PATCH net-next v3 1/3] ethtool: Extend cable testing interface with result source information Oleksij Rempel
2024-08-22 12:07 ` [PATCH net-next v3 2/3] ethtool: Add support for specifying information source in cable test results Oleksij Rempel
2024-08-22 12:07 ` [PATCH net-next v3 3/3] phy: dp83td510: Utilize ALCD for cable length measurement when link is active Oleksij Rempel
2024-08-22 15:50 ` Andrew Lunn
2024-08-26 16:40 ` 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=172469043299.64426.5670112366033990783.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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