From: Stas Sergeev <stsp@list.ru>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, mxs@sbrk.org,
arno@natisbad.org, stsp@users.sourceforge.net,
devicetree@vger.kernel.org, thomas.petazzoni@free-electrons.com
Subject: Re: [PATCH net v5 0/4] net: enable inband link state negotiation only when explicitly requested
Date: Tue, 21 Jul 2015 14:17:40 +0300 [thread overview]
Message-ID: <55AE2A54.3010701@list.ru> (raw)
In-Reply-To: <1437439798-12622-1-git-send-email-f.fainelli@gmail.com>
21.07.2015 03:49, Florian Fainelli пишет:
> Hi all,
>
> Changes in v5:
>
> - removed an invalid use of the link_update callback in the SF2 driver
> was appeared after merging "net: phy: fixed_phy: handle link-down case"
Thanks for bringing this forward!
For the future, perhaps it will make sense to also
teach phylib to never read link status (including speed)
when link is down. Will help to narrow more of such problems.
next prev parent reply other threads:[~2015-07-21 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 0:49 [PATCH net v5 0/4] net: enable inband link state negotiation only when explicitly requested Florian Fainelli
2015-07-21 0:49 ` [PATCH net v5 1/4] net: dsa: bcm_sf2: Do not override speed settings Florian Fainelli
2015-07-21 0:49 ` [PATCH net v5 2/4] net: phy: fixed_phy: handle link-down case Florian Fainelli
2015-07-21 0:49 ` [PATCH net v5 3/4] of_mdio: add new DT property 'managed' to specify the PHY management type Florian Fainelli
2015-07-21 0:49 ` [PATCH net v5 4/4] mvneta: use inband status only when explicitly enabled Florian Fainelli
2015-07-21 11:17 ` Stas Sergeev [this message]
2015-07-21 20:18 ` [PATCH net v5 0/4] net: enable inband link state negotiation only when explicitly requested Arnaud Ebalard
2015-07-21 23:13 ` 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=55AE2A54.3010701@list.ru \
--to=stsp@list.ru \
--cc=arno@natisbad.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mxs@sbrk.org \
--cc=netdev@vger.kernel.org \
--cc=stsp@users.sourceforge.net \
--cc=thomas.petazzoni@free-electrons.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