From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: e1000-devel <e1000-devel@lists.sourceforge.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] e1000: Neaten e1000_config_dsp_after_link_change
Date: Thu, 09 Feb 2012 20:04:54 -0800 [thread overview]
Message-ID: <1328846694.2761.26.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1328846511.1936.4.camel@joe2Laptop>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On Thu, 2012-02-09 at 20:01 -0800, Joe Perches wrote:
> Separate a complicated bit of e1000_config_dsp_after_link_change
> into a new static function e1000_1000Mb_check_cable_length.
>
> Reduces indentation and adds a bit of clarity.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/net/ethernet/intel/e1000/e1000_hw.c | 156
> +++++++++++++--------------
> 1 files changed, 73 insertions(+), 83 deletions(-)
Thank Joe, I have added the patch to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-10 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 4:01 [PATCH net-next] e1000: Neaten e1000_config_dsp_after_link_change Joe Perches
2012-02-10 4:04 ` Jeff Kirsher [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=1328846694.2761.26.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=joe@perches.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).