All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux@armlinux.org.uk, f.fainelli@gmail.com,
	hkallweit1@gmail.com, Vladimir Oltean <olteanv@gmail.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	claudiu.manoil@nxp.com, alexandru.marginean@nxp.com,
	ioana.ciornei@nxp.com, michael@walle.cc
Subject: Re: [PATCH net-next] net: phy: continue searching for C45 MMDs even if first returned ffff:ffff
Date: Thu, 16 Jul 2020 22:09:59 +0200	[thread overview]
Message-ID: <20200716200959.GD1308244@lunn.ch> (raw)
In-Reply-To: <20200716120139.78f6f9a3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Thu, Jul 16, 2020 at 12:01:39PM -0700, Jakub Kicinski wrote:
> On Sun, 12 Jul 2020 19:48:15 +0300 Vladimir Oltean wrote:
> > From: Vladimir Oltean <vladimir.oltean@nxp.com>
> > 
> > At the time of introduction, in commit bdeced75b13f ("net: dsa: felix:
> > Add PCS operations for PHYLINK"), support for the Lynx PCS inside Felix
> > was relying, for USXGMII support, on the fact that get_phy_device() is
> > able to parse the Lynx PCS "device-in-package" registers for this C45
> > MDIO device and identify it correctly.
> > [...]
> 
> PHY folks, is this part of the larger PCS discussion or something
> you're happy to have applied in the current form?

Hi Jakub

This seems fine, independent of the PCS discussions.

     Andrew

  reply	other threads:[~2020-07-16 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 16:48 [PATCH net-next] net: phy: continue searching for C45 MMDs even if first returned ffff:ffff Vladimir Oltean
2020-07-16 19:01 ` Jakub Kicinski
2020-07-16 20:09   ` Andrew Lunn [this message]
2020-07-16 20:12 ` Andrew Lunn
2020-07-16 20:51   ` Vladimir Oltean
2020-07-16 20:58     ` Vladimir Oltean
2020-07-17 17:23 ` David Miller

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=20200716200959.GD1308244@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alexandru.marginean@nxp.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@walle.cc \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.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.