netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: improve stopping PHY
Date: Wed, 16 Jan 2019 20:40:14 +0100	[thread overview]
Message-ID: <20190116194014.GE24870@lunn.ch> (raw)
In-Reply-To: <024c1ea8-6547-b27d-948c-63e32b3229f1@gmail.com>

On Wed, Jan 16, 2019 at 08:20:43PM +0100, Heiner Kallweit wrote:
> phy_stop_interrupts() is called from phy_disconnect() only. Most of
> what it does has been done by phy_stop() already which should have
> been called before phy_disconnect(). Based on that we can do some
> improvements:
> - remove phy_stop_interrupts() and free interrupt in
>   phy_disconnect() directly
> - replace condition "phydev->irq > 0" with the appropriate helper
> - make sure phy state machine is stopped after calling phy_stop()
> - check in phy_disconnect() that PHY is in a stopped state. Else
>   warn to detect misbehaving drivers and call phy_stop().

Hi Heiner

When i see a list like this, it makes me think there should be a
patchset, not a single patch. If something does break, we can bisect
it to just one change.

Please could you try to break this up into a few patches.

Thanks
	Andrew

  reply	other threads:[~2019-01-16 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 19:20 [PATCH net-next] net: phy: improve stopping PHY Heiner Kallweit
2019-01-16 19:40 ` Andrew Lunn [this message]
2019-01-16 20:03   ` Heiner Kallweit

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=20190116194014.GE24870@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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).