public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn•ch>
To: Florian Fainelli <f.fainelli@gmail•com>
Cc: netdev@vger•kernel.org, rmk+kernel@armlinux•org.uk,
	davem@davemloft•net, vivien.didelot@savoirfairelinux•com
Subject: Re: [PATCH net-next v2 3/5] net: phy: phylink: Remove error message
Date: Wed, 13 Dec 2017 17:56:29 +0100	[thread overview]
Message-ID: <20171213165629.GE28466@lunn.ch> (raw)
In-Reply-To: <20171213000029.8649-4-f.fainelli@gmail.com>

On Tue, Dec 12, 2017 at 04:00:27PM -0800, Florian Fainelli wrote:
> Some subsystems like DSA may be trying to connect to a PHY through OF first,
> and then attempt a connect using a local MDIO bus, remove the error message:
> "unable to find PHY node" so we can let MAC drivers whether to print it or not.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail•com>

Reviewed-by: Andrew Lunn <andrew@lunn•ch>

    Andrew

  reply	other threads:[~2017-12-13 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  0:00 [PATCH net-next v2 0/5] PHYLINK preparatory patches for DSA Florian Fainelli
2017-12-13  0:00 ` [PATCH net-next v2 1/5] net: phy: phylink: Allow specifying PHY device flags Florian Fainelli
2017-12-13 16:54   ` Andrew Lunn
2017-12-13  0:00 ` [PATCH net-next v2 2/5] net: phy: phylink: Use PHY device interface if N/A Florian Fainelli
2017-12-13  0:00 ` [PATCH net-next v2 3/5] net: phy: phylink: Remove error message Florian Fainelli
2017-12-13 16:56   ` Andrew Lunn [this message]
2017-12-13  0:00 ` [PATCH net-next v2 4/5] net: phy: phylink: Allow setting a custom link state callback Florian Fainelli
2017-12-13 16:58   ` Andrew Lunn
2017-12-13  0:00 ` [PATCH net-next v2 5/5] net: phy: phylink: Report MoCA as PORT_BNC Florian Fainelli
2017-12-13 16:59   ` Andrew Lunn
2017-12-13 20:55 ` [PATCH net-next v2 0/5] PHYLINK preparatory patches for DSA 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=20171213165629.GE28466@lunn.ch \
    --to=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rmk+kernel@armlinux$(echo .)org.uk \
    --cc=vivien.didelot@savoirfairelinux$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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