From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, gospo@redhat.com,
sassmann@redhat.com
Subject: Re: [net-next 1/2] Documentation/networking/: Update Intel wired LAN driver documentation
Date: Fri, 23 Aug 2013 17:09:40 -0700 [thread overview]
Message-ID: <1377302980.3939.91.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1377262419.3364.11.camel@bwh-desktop.uk.level5networks.com>
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
On Fri, 2013-08-23 at 13:53 +0100, Ben Hutchings wrote:
> On Fri, 2013-08-23 at 05:29 -0700, Jeff Kirsher wrote:
> > Updates the documentation to the Intel wired LAN drivers.
>
> Except e100.txt which seems to be moving backward in time:
>
> [...]
> > --- a/Documentation/networking/e100.txt
> > +++ b/Documentation/networking/e100.txt
> > @@ -1,7 +1,7 @@
> > Linux* Base Driver for the Intel(R) PRO/100 Family of Adapters
> > ==============================================================
> >
> > -November 15, 2005
> > +March 15, 2011
> >
> > Contents
> > ========
> > @@ -94,8 +94,8 @@ Additional Configurations
> >
> > Configuring a network driver to load properly when the system is started is
> > distribution dependent. Typically, the configuration process involves adding
> > - an alias line to /etc/modprobe.d/*.conf as well as editing other system
> > - startup scripts and/or configuration files. Many popular Linux
> > + an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing
>
> Reverting this fix:
>
> commit 970e2486492aa1eb47a436a5a4c81e92558986a9
> Author: Lucas De Marchi <lucas.demarchi@profusion.mobi>
> Date: Fri Mar 30 13:37:16 2012 -0700
>
> Documentation: remove references to /etc/modprobe.conf
>
> [...]
> > Enabling Wake on LAN* (WoL)
> > ---------------------------
> > - WoL is provided through the ethtool* utility. For instructions on enabling
> > - WoL with ethtool, refer to the ethtool man page.
> > + WoL is provided through the ethtool* utility. The ethtool utility is included
> > + with Red Hat* 8.0. For other Linux distributions, download and install
> [...]
>
> And part of this one:
>
> commit 68f20d948c86bd6bbc075052f6b6c45b8f56957e
> Author: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Fri Dec 17 12:14:34 2010 +0000
>
> Documentation/networking: Update Intel Wired LAN docs
>
> Mentioning a 2002 distribution is completely pointless.
>
> Ben.
>
Thanks Ben, I will drop all the e100.txt changes at this point. The
driver has little to no changes in the last couple of years, so the
documentation should not be changing.
I will re-spin with a v2.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-08-24 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 12:29 [net-next 1/2] Documentation/networking/: Update Intel wired LAN driver documentation Jeff Kirsher
2013-08-23 12:29 ` [net-next 2/2] e1000e: balance semaphore put/get for 82573 Jeff Kirsher
2013-08-23 12:53 ` [net-next 1/2] Documentation/networking/: Update Intel wired LAN driver documentation Ben Hutchings
2013-08-24 0:09 ` 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=1377302980.3939.91.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
/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