netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, andrew@lunn.ch,
	Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH net 0/2] net: phy: Unbind/bind fixes
Date: Tue, 7 Feb 2017 22:47:01 -0800	[thread overview]
Message-ID: <fe3a0be5-dca4-c0d9-43b2-9da40394bfdc@gmail.com> (raw)
In-Reply-To: <20170205222557.24739-1-f.fainelli@gmail.com>



On 02/05/2017 02:25 PM, Florian Fainelli wrote:
> Hi all,
> 
> This patch series addresses the inability to safely unbind and bind
> PHY drivers by making the appropriate checks throught PHYLIB where we
> may be directly responding to user-space queries, as well as from within
> the kernel state machine.
> 
> The second patch makes the unbind -> bind working by taking care of the
> PHY state machine state.

I need to make another set of fixes after "net: phy: Fix lack of
reference count on PHY driver" because the Generic PHY driver is of
course behaving differently and my testing was focused on every other
one but this one which is built-in...

> 
> Florian Fainelli (2):
>   net: phy: Check phydev->drv
>   net: phy: Fix PHY driver bind and unbind events
> 
>  drivers/net/phy/phy.c        | 26 ++++++++++++++++++++++----
>  drivers/net/phy/phy_device.c | 27 +++++++++++++++++++++++++--
>  include/linux/phy.h          |  3 +++
>  3 files changed, 50 insertions(+), 6 deletions(-)
> 

-- 
Florian

      parent reply	other threads:[~2017-02-08  6:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 22:25 [PATCH net 0/2] net: phy: Unbind/bind fixes Florian Fainelli
2017-02-05 22:25 ` [PATCH net 1/2] net: phy: Check phydev->drv Florian Fainelli
2017-02-05 22:25 ` [PATCH net 2/2] net: phy: Fix PHY driver bind and unbind events Florian Fainelli
2017-02-08  6:47 ` Florian Fainelli [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=fe3a0be5-dca4-c0d9-43b2-9da40394bfdc@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).