All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sven Eckelmann <se@simonwunderlich.de>
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,
	linux-kernel@vger.kernel.org, sw@simonwunderlich.de,
	ih@simonwunderlich.de
Subject: Re: [PATCH] net: phy: realtek: Add RTL8224 cable testing support
Date: Wed, 29 Oct 2025 01:50:09 +0000	[thread overview]
Message-ID: <176170260974.2460121.14328478354659029522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251024-rtl8224-cable-test-v1-1-e3cda89ac98f@simonwunderlich.de>

Hello:

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

On Fri, 24 Oct 2025 11:49:00 +0200 you wrote:
> From: Issam Hamdi <ih@simonwunderlich.de>
> 
> The RTL8224 can detect open pairs and short types (in same pair or some
> other pair). The distance to this problem can be estimated. This is done
> for each of the 4 pairs separately.
> 
> It is not meant to be run while there is an active link partner because
> this interferes with the active test pulses.
> 
> [...]

Here is the summary with links:
  - net: phy: realtek: Add RTL8224 cable testing support
    https://git.kernel.org/netdev/net-next/c/61958b33ef0b

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



      parent reply	other threads:[~2025-10-29  1:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  9:49 [PATCH] net: phy: realtek: Add RTL8224 cable testing support Sven Eckelmann
2025-10-27  0:16 ` Andrew Lunn
2025-10-27  7:49   ` Sven Eckelmann
2025-10-27 11:55     ` Andrew Lunn
2025-10-29  1: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=176170260974.2460121.14328478354659029522.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=ih@simonwunderlich.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=se@simonwunderlich.de \
    --cc=sw@simonwunderlich.de \
    /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.