From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: jeffrey.t.kirsher@intel.com, davem@davemleft.org,
netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com
Subject: Re: [net-next-2.6 03/27] Documentation/networking/igb.txt: update documentation
Date: Fri, 10 Dec 2010 12:21:49 -0800 (PST) [thread overview]
Message-ID: <20101210.122149.232731880.davem@davemloft.net> (raw)
In-Reply-To: <1291996224.11673.2.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 10 Dec 2010 15:50:24 +0000
> On Fri, 2010-12-10 at 01:50 -0800, Jeff Kirsher wrote:
>> Update Intel Wired LAN igb documentation.
>>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> ---
>> Documentation/networking/igb.txt | 22 +++++++++++++++++++---
>> 1 files changed, 19 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/networking/igb.txt b/Documentation/networking/igb.txt
>> index ab2d718..393bdb7 100644
>> --- a/Documentation/networking/igb.txt
>> +++ b/Documentation/networking/igb.txt
>> @@ -36,6 +36,7 @@ Default Value: 0
>> This parameter adds support for SR-IOV. It causes the driver to spawn up to
>> max_vfs worth of virtual function.
>>
>> +
>> Additional Configurations
>> =========================
>>
>> @@ -60,7 +61,8 @@ Additional Configurations
>> Ethtool
>> -------
>> The driver utilizes the ethtool interface for driver configuration and
>> - diagnostics, as well as displaying statistical information.
>> + diagnostics, as well as displaying statistical information. The latest
>> + version of Ethtool can be found at:
>>
>> http://sourceforge.net/projects/gkernel.
>
> Please update this to:
> http://ftp.kernel.org/pub/software/network/ethtool/
Indeed.
Intel folks, please address all of Ben's feedback and respin this
pull request, thanks.
next prev parent reply other threads:[~2010-12-10 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:50 [net-next 00/27][pull-request] Intel Wired LAN Driver Updates Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 01/27] Documentation/networking/e1000.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 02/27] Documentation/networking/e1000e.txt: " Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 03/27] Documentation/networking/igb.txt: update documentation Jeff Kirsher
2010-12-10 15:50 ` Ben Hutchings
2010-12-10 20:21 ` David Miller [this message]
2010-12-11 5:26 ` Jeff Kirsher
2010-12-11 5:25 ` Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 04/27] Documentation/networking/igbvf.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 05/27] Documentation/networking/ixgbe.txt: Update ixgbe documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 06/27] Documentation/networking/ixgbevf.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 07/27] MAINTAINERS: Update Intel Wired LAN info Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 08/27] e1000: fix return value not set on error Jeff Kirsher
2010-12-10 9:50 ` Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 09/27] Intel Wired LAN drivers: Use static const Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 10/27] ixgb: Don't check for vlan group on transmit Jeff Kirsher
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=20101210.122149.232731880.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=bphilips@novell.com \
--cc=davem@davemleft.org \
--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).