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: micrel: use phy_read_mmd and phy_write_mmd
Date: Wed, 16 Jan 2019 22:32:39 +0100 [thread overview]
Message-ID: <20190116213239.GJ29244@lunn.ch> (raw)
In-Reply-To: <b868d66d-c66a-fe6d-fcfc-54dc9ec875d5@gmail.com>
On Wed, Jan 16, 2019 at 09:52:22PM +0100, Heiner Kallweit wrote:
> This driver implements open-coded versions of phy_read_mmd() and
> phy_write_mmd() for KSZ9031. That's not needed, let's use the
> phylib functions directly.
>
> This is compile-tested only because I have no such hardware.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-01-16 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 20:52 [PATCH net-next] net: phy: micrel: use phy_read_mmd and phy_write_mmd Heiner Kallweit
2019-01-16 21:32 ` Andrew Lunn [this message]
2019-01-17 23:11 ` 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=20190116213239.GJ29244@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).