Hi Tom,
> Hi Hannes,
>
> > Negative phy-addresses can occour if the caller function was not
> > able to determine a valid phy address (from device-tree for
> > example). In this case we catch this here and search for ANY phy
> > device on the given mdio- bus.
> >
> > Signed-off-by: Hannes Schmel
Hi Hannes,
> Negative phy-addresses can occour if the caller function was not able
> to determine a valid phy address (from device-tree for example). In
> this case we catch this here and search for ANY phy device on the
> given mdio- bus.
>
> Signed-off-by: Hannes Schmelzer
>
> ---
>
> Change
On 29. 03. 19 9:54, Hannes Schmelzer wrote:
> Negative phy-addresses can occour if the caller function was not able to
> determine a valid phy address (from device-tree for example). In this
> case we catch this here and search for ANY phy device on the given mdio-
> bus.
>
> Signed-off-by: Hannes
Negative phy-addresses can occour if the caller function was not able to
determine a valid phy address (from device-tree for example). In this
case we catch this here and search for ANY phy device on the given mdio-
bus.
Signed-off-by: Hannes Schmelzer
---
Changes in v3:
- fix commit message
C
4 matches
Mail list logo