From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, zefir.kurtisi@neratec.com,
sebastian.hesselbarth@gmail.com, w-kwok2@ti.com,
m-karicheri2@ti.com, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com, tremyfr@gmail.com,
sergei.shtylyov@cogentembedded.com, jszhang@marvell.com,
jarod@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] net: Incorrect use of phy_read_status()
Date: Tue, 07 Feb 2017 13:48:46 -0500 (EST) [thread overview]
Message-ID: <20170207.134846.1084414639114098837.davem@davemloft.net> (raw)
In-Reply-To: <20170206235523.23216-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 6 Feb 2017 15:55:19 -0800
> This patch series removes incorrect uses of phy_read_status() which can clobber
> the PHY device link while we are executing with the state machine running.
>
> greth was potentially another candidate, but it does funky stuff with
> auto-negotation that I am still trying to understand.
Series applied, thanks.
prev parent reply other threads:[~2017-02-07 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 23:55 [PATCH net-next 0/4] net: Incorrect use of phy_read_status() Florian Fainelli
2017-02-06 23:55 ` [PATCH net-next 1/4] net: mv643xx_eth: Do not clobber PHY link outside of state machine Florian Fainelli
2017-02-07 0:13 ` Andrew Lunn
2017-02-06 23:55 ` [PATCH net-next 2/4] net: pxa168_eth: " Florian Fainelli
2017-02-06 23:55 ` [PATCH net-next 3/4] net: netcp: " Florian Fainelli
2017-02-06 23:55 ` [PATCH net-next 4/4] net: dsa: " Florian Fainelli
2017-02-07 0:11 ` Andrew Lunn
2017-02-07 11:42 ` David Laight
2017-02-07 13:14 ` Andrew Lunn
2017-02-07 18:48 ` David Miller [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=20170207.134846.1084414639114098837.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jarod@redhat.com \
--cc=jszhang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tremyfr@gmail.com \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=w-kwok2@ti.com \
--cc=zefir.kurtisi@neratec.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).