From: Ben Hutchings <bhutchings@solarflare.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, gospo@redhat.com,
bphilips@novell.com
Subject: Re: [PATCH 04/27] Documentation/networking/igbvf.txt: Update documentation
Date: Sat, 11 Dec 2010 06:34:09 +0000 [thread overview]
Message-ID: <1292049249.3136.28.camel@localhost> (raw)
In-Reply-To: <1292048241-22026-5-git-send-email-jeffrey.t.kirsher@intel.com>
On Fri, 2010-12-10 at 22:16 -0800, Jeff Kirsher wrote:
> Update Intel Wired LAN igbvf documentation.
>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> Documentation/networking/igbvf.txt | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/networking/igbvf.txt b/Documentation/networking/igbvf.txt
> index 0560281..694817b 100644
> --- a/Documentation/networking/igbvf.txt
> +++ b/Documentation/networking/igbvf.txt
> @@ -58,7 +58,9 @@ 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. Ethtool
> + version 3.0 or later is required for this functionality, although we
> + strongly recommend downloading the latest version at:
>
> http://sourceforge.net/projects/gkernel.
Do I have to point out every instance of this URL individually?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-12-11 6:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 6:16 [net-next 00/27][pull-request] Intel Wired LAN Driver Updates Jeff Kirsher
2010-12-11 6:16 ` [PATCH 01/27] Documentation/networking/e1000.txt: Update documentation Jeff Kirsher
2010-12-11 6:16 ` [PATCH 02/27] Documentation/networking/e1000e.txt: " Jeff Kirsher
2010-12-11 6:16 ` [PATCH 03/27] Documentation/networking/igb.txt: update documentation Jeff Kirsher
2010-12-11 6:16 ` [PATCH 04/27] Documentation/networking/igbvf.txt: Update documentation Jeff Kirsher
2010-12-11 6:34 ` Ben Hutchings [this message]
[not found] ` <AANLkTikUqZsaSg-q+GJvRrUb4C8rFZSbBta0tyeh==Ay@mail.gmail.com>
2010-12-11 19:44 ` David Miller
2010-12-11 6:16 ` [PATCH 05/27] Documentation/networking/ixgbe.txt: Update ixgbe documentation Jeff Kirsher
2010-12-11 6:17 ` [PATCH 06/27] Documentation/networking/ixgbevf.txt: Update documentation Jeff Kirsher
2010-12-11 6:17 ` [PATCH 07/27] MAINTAINERS: Update Intel Wired LAN info Jeff Kirsher
2010-12-11 6:17 ` [PATCH 08/27] e1000: fix return value not set on error Jeff Kirsher
2010-12-11 6:17 ` Jeff Kirsher
2010-12-11 6:17 ` [PATCH 09/27] Intel Wired LAN drivers: Use static const Jeff Kirsher
2010-12-11 6:17 ` [PATCH 10/27] ixgb: Don't check for vlan group on transmit Jeff Kirsher
2010-12-13 1:00 ` Jesse Gross
2010-12-13 18:43 ` Tantilov, Emil S
2010-12-14 3:40 ` Jesse Gross
2010-12-14 18:00 ` Tantilov, Emil S
2010-12-11 19:44 ` [net-next 00/27][pull-request] Intel Wired LAN Driver Updates 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=1292049249.3136.28.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=bphilips@novell.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.