netdev - Re: [PATCH 2/6] e1000e: remove namespace collisions with e1000

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <46C21D07.6060108@intel.com>
Date:	Tue, 14 Aug 2007 14:22:15 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	Rick Jones <rick.jones2@...com>,
	Auke Kok <auke-jan.h.kok@...el.com>, netdev@...r.kernel.org,
	akpm@...ux-foundation.org, andi@...stfloor.org
Subject: Re: [PATCH 2/6] e1000e: remove namespace collisions with e1000

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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html