All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
Date: Thu, 10 Jun 2021 20:40:07 +0000	[thread overview]
Message-ID: <162335760748.27474.16543294261653602256.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210607023645.2958840-1-vee.khee.wong@linux.intel.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Mon,  7 Jun 2021 10:36:45 +0800 you wrote:
> PHY devices such as the Marvell Alaska 88E2110 does not return a valid
> PHY ID when probed using Clause-22. The current implementation treats
> PHY ID of zero as a non-error and valid PHY ID, and causing the PHY
> device failed to bind to the Marvell driver.
> 
> For such devices, we do an additional probe in the Clause-45 space,
> if a valid PHY ID is returned, we then proceed to attach the PHY
> device to the matching PHY ID driver.
> 
> [...]

Here is the summary with links:
  - [net-next,1/1] net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
    https://git.kernel.org/netdev/net-next/c/b040aab76323

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



      parent reply	other threads:[~2021-06-10 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  2:36 [PATCH net-next 1/1] net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space Wong Vee Khee
2021-06-10  4:05 ` Andrew Lunn
2021-06-10 20: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=162335760748.27474.16543294261653602256.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=vee.khee.wong@linux.intel.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 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.