From: Andrew Lunn <andrew@lunn.ch>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
vivien.didelot@savoirfairelinux.com,
Fabian Frederick <fabf@skynet.be>,
Pavel Nakonechny <pavel.nakonechny@skitlab.ru>,
Joe Perches <joe@perches.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
nbd@openwrt.org, sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH 0/3] Refactor nested mdiobus read/write functions
Date: Thu, 22 Oct 2015 15:18:31 +0200 [thread overview]
Message-ID: <20151022131831.GG1985@lunn.ch> (raw)
In-Reply-To: <5628A059.1020402@baylibre.com>
On Thu, Oct 22, 2015 at 10:37:45AM +0200, Neil Armstrong wrote:
> In order to avoid locked signal false positive for nested mdiobus
> read/write calls, nested code was introduced in mv88e6xxx and
> mdio-mux.
> But mv88e6060 also needs such nested mdiobus read/write calls.
> For sake of refactoring, introduce nested variants of mdiobus read/write
> and make them used by mv88e6xxx and mv88e6060.
> In a next patch, mdio-mux should also use these variant calls.
>
> Neil Armstrong (3):
> net: phy: Add nested variants of mdiobus read/write
> net: dsa: Make mv88e6xxx use nested mdiobus read/write
> net: dsa: Make mv88e6060 use nested mdiobus read/write
>
> drivers/net/dsa/mv88e6060.c | 4 ++--
> drivers/net/dsa/mv88e6xxx.c | 46 ++++++++-----------------------------
> drivers/net/phy/mdio_bus.c | 55 +++++++++++++++++++++++++++++++++++++++++++++
> include/linux/phy.h | 2 ++
> 4 files changed, 68 insertions(+), 39 deletions(-)
Hi Neil
Thanks for refactoring.
Reviewd-by: Andrew Lunn <andrew@lunn.ch>
Tested-by: Andrew Lunn <andrew@lunn.ch>
I tested with a 88E6172 and lockdep enabled.
Thanks
Andrew
next prev parent reply other threads:[~2015-10-22 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 8:37 [PATCH 0/3] Refactor nested mdiobus read/write functions Neil Armstrong
2015-10-22 13:18 ` Andrew Lunn [this message]
2015-10-23 13:00 ` 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=20151022131831.GG1985@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fabf@skynet.be \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=narmstrong@baylibre.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=pavel.nakonechny@skitlab.ru \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vivien.didelot@savoirfairelinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.