From: "Kok, Auke" <auke-jan.h.kok@intel•com>
To: Jeff Garzik <jeff@garzik•org>
Cc: Rick Jones <rick.jones2@hp•com>,
Auke Kok <auke-jan.h.kok@intel•com>,
netdev@vger•kernel.org, akpm@linux-foundation•org,
andi@firstfloor•org
Subject: Re: [PATCH 2/6] e1000e: remove namespace collisions with e1000
Date: Tue, 14 Aug 2007 14:22:15 -0700 [thread overview]
Message-ID: <46C21D07.6060108@intel.com> (raw)
In-Reply-To: <46C1DB49.1080601@hp.com>
Rick Jones wrote:
>> if you grep around this effort was already started using the 'e1e_'
>> prefix. I like the shorter prefix, but your call ultimately. Either
>> way, make sure to make the driver consistent there too.
>
> should it then be consistent with the overall driver name too?
> certainly calling things e1e or e1ke or heck, even elke if one wanted
> to be a triffle playful would certainly help distinguish this driver
> from its grandfather.
I think we are passed the time for the name-a-driver raffle now. We've informed
a lot of people that the name will be "e1000e", so I definately prefer using
this internally as well.
As for the e1000_get_speed_and_duplex_fiber_serdes long names, those are an
eyesore to me as well...
Auke
next prev parent reply other threads:[~2007-08-14 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 20:00 [PATCH 1/6] e1000e: Fix header includes [v2] Auke Kok
2007-08-10 20:00 ` [PATCH 2/6] e1000e: remove namespace collisions with e1000 Auke Kok
2007-08-14 5:13 ` Jeff Garzik
2007-08-14 16:41 ` Rick Jones
2007-08-14 21:22 ` Kok, Auke [this message]
2007-08-10 20:00 ` [PATCH 3/6] e1000e: Use dma_alloc_coherent where possible Auke Kok
2007-08-10 20:00 ` [PATCH 4/6] e1000e: Use time_after to account for jiffies wrapping Auke Kok
2007-08-10 20:01 ` [PATCH 5/6] e1000e: error handling for pci_map_single calls Auke Kok
2007-08-14 5:15 ` Jeff Garzik
2007-08-10 20:01 ` [PATCH 6/6] e1000e: Remove two compile warnings Auke Kok
2007-08-14 5:11 ` [PATCH 1/6] e1000e: Fix header includes [v2] Jeff Garzik
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=46C21D07.6060108@intel.com \
--to=auke-jan.h.kok@intel$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andi@firstfloor$(echo .)org \
--cc=jeff@garzik$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rick.jones2@hp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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