From: Alexander Kochetkov <al.kochet@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Roger Quadros <rogerq@ti.com>,
Madalin Bucur <madalin.bucur@nxp.com>
Cc: Alexander Kochetkov <al.kochet@gmail.com>
Subject: [PATCH v1] net: phy: fix auto-negotiation stall due to unavailable interrupt
Date: Thu, 20 Apr 2017 14:00:03 +0300 [thread overview]
Message-ID: <1492686004-30527-1-git-send-email-al.kochet@gmail.com> (raw)
Hello Florian, Roger and Madalin!
This is slightly modified version of previous patch[1].
It take into account that phy_start_aneg() may be called from
differend places not only from PHY state machine. So the patch
use phy_trigger_machine() to schedule link state update
correctly.
I borrow some text from Roger's commit message.
Added 'Cc: stable <stable@vger.kernel.org> tag'
because the problem exist on 4.9 and 4.10 branches.
Don't know what commit brake the code, so I don't add
Fixes tag.
Roger, could you please test this one patch?
Madalin, I found, that you tested Roger’s patch[2] and this
one patch will get upstream instead of patch[2]. Could you
please test it?
Regards,
Alexander.
[1] http://patchwork.ozlabs.org/patch/743773/
[2] https://lkml.org/lkml/2017/3/30/517
Alexander Kochetkov (1):
net: phy: fix auto-negotiation stall due to unavailable interrupt
drivers/net/phy/phy.c | 40 ++++++++++++++++++++++++++++++++++++----
include/linux/phy.h | 1 +
2 files changed, 37 insertions(+), 4 deletions(-)
--
1.7.9.5
next reply other threads:[~2017-04-20 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 11:00 Alexander Kochetkov [this message]
2017-04-20 11:00 ` [PATCH v1] net: phy: fix auto-negotiation stall due to unavailable interrupt Alexander Kochetkov
2017-04-20 15:33 ` Alexander Kochetkov
2017-04-21 14:18 ` Roger Quadros
2017-04-21 14:42 ` Alexander Kochetkov
2017-04-25 14:36 ` David Miller
2017-04-25 15:25 ` Alexander Kochetkov
2017-04-25 20:09 ` Alexandre Belloni
2017-04-25 20:26 ` David Miller
2017-04-25 21:07 ` Florian Fainelli
2017-04-26 10:21 ` Alexandre Belloni
2017-04-26 18:36 ` 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=1492686004-30527-1-git-send-email-al.kochet@gmail.com \
--to=al.kochet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=sergei.shtylyov@cogentembedded.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 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).