mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Clark Wang <xiaoning.wang@nxp.com>
Cc: andrei.botila@oss.nxp.com, andrew@lunn.ch, ansuelsmth@gmail.com,
	davem@davemloft.net, edumazet@google.com, hkallweit1@gmail.com,
	kuba@kernel.org, pabeni@redhat.com, rmk+kernel@armlinux.org.uk,
	sd@queasysnail.net, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	imx@lists.linux.dev
Subject: Re: [PATCH net] net: phy: nxp-c45-tja11xx: fix the PHY ID mismatch issue when using C45
Date: Tue, 12 Aug 2025 10:40:07 +0000	[thread overview]
Message-ID: <175499520750.2526251.1270077410677904489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807040832.2455306-1-xiaoning.wang@nxp.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu,  7 Aug 2025 12:08:32 +0800 you wrote:
> TJA1103/04/20/21 support both C22 and C45 accessing methods.
> 
> The TJA11xx driver has implemented the match_phy_device() API.
> However, it does not handle the C45 ID. If C45 was used to access
> TJA11xx, match_phy_device() would always return false due to
> phydev->phy_id only used by C22 being empty, resulting in the
> generic phy driver being used for TJA11xx PHYs.
> 
> [...]

Here is the summary with links:
  - [net] net: phy: nxp-c45-tja11xx: fix the PHY ID mismatch issue when using C45
    https://git.kernel.org/netdev/net/c/8ee90742cf29

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



      reply	other threads:[~2025-08-12 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07  4:08 Clark Wang
2025-08-12 10: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=175499520750.2526251.1270077410677904489.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrei.botila@oss.nxp.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=imx@lists.linux.dev \
    --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=rmk+kernel@armlinux.org.uk \
    --cc=sd@queasysnail.net \
    --cc=xiaoning.wang@nxp.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
all inboxes | Powered by JetHome®