From: Randy Dunlap <randy.dunlap@oracle.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>,
NetDev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH -MM] e1000: rewrite hardware initialization code
Date: Tue, 9 Jan 2007 11:24:16 -0800 [thread overview]
Message-ID: <20070109112416.266efb84.randy.dunlap@oracle.com> (raw)
In-Reply-To: <m3fyakau44.fsf@defiant.localdomain>
On Tue, 09 Jan 2007 20:16:27 +0100 Krzysztof Halasa wrote:
> Auke Kok <auke-jan.h.kok@intel.com> writes:
>
> > drivers/net/e1000/Makefile | 19
> > drivers/net/e1000/e1000.h | 95
> > drivers/net/e1000/e1000_80003es2lan.c | 1330 +++++
> > drivers/net/e1000/e1000_80003es2lan.h | 89
> > drivers/net/e1000/e1000_82540.c | 586 ++
> > drivers/net/e1000/e1000_82541.c | 1164 ++++
> > drivers/net/e1000/e1000_82541.h | 86
> > drivers/net/e1000/e1000_82542.c | 466 ++
> > drivers/net/e1000/e1000_82543.c | 1397 +++++
> > drivers/net/e1000/e1000_82543.h | 45
> > drivers/net/e1000/e1000_82571.c | 1132 ++++
> > drivers/net/e1000/e1000_82571.h | 42
>
> Perhaps the "e1000_" prefix could be dropped as redundant?
> --
Yes, that suggestion would agree with what Linus told us about
usb file names 7 years ago. (huh? that long?)
---
~Randy
next prev parent reply other threads:[~2007-01-09 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 17:36 [PATCH -MM] e1000: rewrite hardware initialization code Auke Kok
2007-01-09 18:33 ` Stephen Hemminger
2007-01-09 18:48 ` Auke Kok
2007-01-09 18:45 ` Andrew Morton
2007-01-09 19:10 ` Auke Kok
2007-01-09 22:24 ` Auke Kok
2007-01-09 19:16 ` Krzysztof Halasa
2007-01-09 19:24 ` Randy Dunlap [this message]
2007-01-09 19:45 ` Auke Kok
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=20070109112416.266efb84.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jgarzik@pobox.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--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).