From: David Daney <ddaney@caviumnetworks.com>
To: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: David Daney <ddaney@caviumnetworks.com>,
Cyril Chemparathy <cyril@ti.com>,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: [PATCH 0/2] phylib: Cleanup marvell.c and add 88E1149R support.
Date: Fri, 19 Nov 2010 13:58:51 -0800 [thread overview]
Message-ID: <1290203933-28251-1-git-send-email-ddaney@caviumnetworks.com> (raw)
This is the second iteration of this patch. I have split out the
device tree support from the first version to a different patch set.
The 88E1149R support is useful 'stand alone', so if it is acceptable,
it can be merged first.
The first patch is a small cleanup suggested by Cyril Chemparathy, the
second one adds basic 88E1149R support.
David Daney (2):
phylib: Use common page register definition for Marvell PHYs.
phylib: Add support for Marvell 88E1149R devices.
drivers/net/phy/marvell.c | 67 ++++++++++++++++++++++++++++++++++--------
include/linux/marvell_phy.h | 1 +
2 files changed, 55 insertions(+), 13 deletions(-)
Cc: Cyril Chemparathy <cyril@ti.com>
Cc: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Wolfram Sang <w.sang@pengutronix.de>
--
1.7.2.3
next reply other threads:[~2010-11-19 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 21:58 David Daney [this message]
2010-11-19 21:58 ` [PATCH 1/2] phylib: Use common page register definition for Marvell PHYs David Daney
2010-11-19 21:58 ` [PATCH 2/2] phylib: Add support for Marvell 88E1149R devices David Daney
2010-11-22 16:34 ` [PATCH 0/2] phylib: Cleanup marvell.c and add 88E1149R support 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=1290203933-28251-1-git-send-email-ddaney@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=arnaud.patard@rtp-net.org \
--cc=benh@kernel.crashing.org \
--cc=cyril@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®