From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, bruce.w.allan@intel.com
Subject: Re: [net-next-2.6 PATCH 3/9] e1000e: provide family-specific PHY power up/down operations
Date: Wed, 02 Dec 2009 00:37:49 -0800 (PST) [thread overview]
Message-ID: <20091202.003749.173515426.davem@davemloft.net> (raw)
In-Reply-To: <20091202014720.396.29751.stgit@localhost.localdomain>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Tue, 01 Dec 2009 17:47:22 -0800
> From: Bruce Allan <bruce.w.allan@intel.com>
>
> The different families (80003es2lan, 8257x, ICHx/PCH) supported by the
> driver each have their own conditions when the PHY can be powered down.
> This patch rewrites the PHY power up/down code to fit with the family-
> specific style used in the driver. All pre-existing calls to power up or
> down the PHY remain untouched. A new call to power down the PHY when
> removing the driver when the interface is down replaces the current call
> to reset the PHY in order to reduce power consumption.
>
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Applied.
next prev parent reply other threads:[~2009-12-02 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 1:46 [net-next-2.6 PATCH 1/9] e1000e: provide family-specific functions to manage VLAN filter arrays Jeff Kirsher
2009-12-02 1:47 ` [net-next-2.6 PATCH 2/9] e1000e: guard against buffer overflow in cable length tables Jeff Kirsher
2009-12-02 8:37 ` David Miller
2009-12-02 1:47 ` [net-next-2.6 PATCH 3/9] e1000e: provide family-specific PHY power up/down operations Jeff Kirsher
2009-12-02 8:37 ` David Miller [this message]
2009-12-02 8:37 ` [net-next-2.6 PATCH 1/9] e1000e: provide family-specific functions to manage VLAN filter arrays 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=20091202.003749.173515426.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bruce.w.allan@intel.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.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).