Devicetree
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, Frank.Sae@motor-comm.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, hkallweit1@gmail.com,
	linux@armlinux.org.uk, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] net: phy: motorcomm: Add cable test support for internal YT861x PHYs
Date: Fri, 16 Oct 2026 01:10:08 +0000	[thread overview]
Message-ID: <179211300813.4187796.258497069495042661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009175936.428256-1-mmyangfl@gmail.com>

Hello:

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

On Sat, 10 Oct 2026 01:59:29 +0800 you wrote:
> The YT921x switches integrate GbE PHYs of the YT861x family (PHY ID
> 0x01e04281) on the switch-internal MDIO bus exposed by the yt921x DSA
> driver. Add a driver entry and TDR cable test support.
> 
> v3:
>  - add dt-bindings
>  - add PHY_IS_INTERNAL
> v2: https://lore.kernel.org/r/20261006202352.1616626-1-mmyangfl@gmail.com
>  - split into a driver entry patch and a cable test patch
>  - update comments and kconfig
>  - add yt861x_config_init() and apply the auto sleep setting, restore auto
>    sleep when starting the TDR test fails
>  - use separate variables for the TDR status
> v1: https://lore.kernel.org/r/20261004184246.1260426-1-mmyangfl@gmail.com
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/3] dt-bindings: net: motorcomm: Add YT861x PHY compatible
    https://git.kernel.org/netdev/net-next/c/1202140b297e
  - [net-next,v3,2/3] net: phy: motorcomm: Add driver entry for internal YT861x PHYs
    https://git.kernel.org/netdev/net-next/c/ae0c7e8d0bab
  - [net-next,v3,3/3] net: phy: motorcomm: Add cable test support for internal YT861x PHYs
    https://git.kernel.org/netdev/net-next/c/fc697291ad0a

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



      parent reply	other threads:[~2026-10-16  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 17:59 [PATCH net-next v3 0/3] net: phy: motorcomm: Add cable test support for internal YT861x PHYs David Yang
2026-10-09 17:59 ` [PATCH net-next v3 1/3] dt-bindings: net: motorcomm: Add YT861x PHY compatible David Yang
2026-10-09 18:41   ` Conor Dooley
2026-10-09 17:59 ` [PATCH net-next v3 2/3] net: phy: motorcomm: Add driver entry for internal YT861x PHYs David Yang
2026-10-09 17:59 ` [PATCH net-next v3 3/3] net: phy: motorcomm: Add cable test support " David Yang
2026-10-13  1:58   ` Andrew Lunn
2026-10-16  1:10 ` 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=179211300813.4187796.258497069495042661.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Frank.Sae@motor-comm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mmyangfl@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    /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