From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Enhanced ethtool API of CPSW driver in order to be able to address even more than one PHY.
Date: Thu, 21 Apr 2011 20:11:56 +0300 [thread overview]
Message-ID: <20110421165014.GA2035@nataf.siach.name> (raw)
In-Reply-To: <1303402638-29884-1-git-send-email-sven.fischer@snom.com>
Hi Sven,
On Thu, Apr 21, 2011 at 06:17:18PM +0200, Sven Fischer wrote:
> Linked ethtool ioctls ETHTOOL_GSET and ETHTOOL_SSET to the CPSW switch driver and added a new ioctl ETHTOOL_GPHYLINK.
>
> The new ETHTOOL_GPHYLINK, which gets the PHY link status of a specific PHY, makes ETHTOOL_GLINK obsolete, because it was not working PHY specific.
>
> ETHTOOL_GSET and ETHTOOL_SSET ioctls are now able to access a specific PHY as well.
A few comments:
1. Please wrap the patch description lines at 80 characters
2. You should Cc the networking devices mailing list at netdev at vger.kernel.org
on this patch
3. Please separate changes to generic code (like ethtool, phy) from changes to
a specific driver (like cpsw).
By the way, this cpsw driver does not appear to exist in the current mainline
kernel. When sending a patch against a development tree, please specify which
one.
baruch
> ---
> drivers/net/cpsw.c | 53 +++++++++++++++++++++++++++++++++++++++++++++++
> drivers/net/phy/phy.c | 9 ++++++++
> include/linux/ethtool.h | 12 +++++++++-
> include/linux/phy.h | 1 +
> net/core/ethtool.c | 28 ++++++++++++++++++++++++-
> 5 files changed, 101 insertions(+), 2 deletions(-)
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2011-04-21 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 16:17 [PATCH] Enhanced ethtool API of CPSW driver in order to be able to address even more than one PHY Sven Fischer
2011-04-21 17:11 ` Baruch Siach [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=20110421165014.GA2035@nataf.siach.name \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.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