netdev - Re: [RFC] Moving files around in drivers/net

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Jun 2011 07:23:57 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
cc:	Joe Perches <joe@...ches.com>, netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Paul Gortmaker <paul.gortmaker@...driver.com>
Subject: Re: [RFC] Moving files around in drivers/net


On Monday 2011-06-20 04:25, Jeff Kirsher wrote:
>> pktgen in hamachi/yellowfin should be pkteng
>> 
>> I think it might be better if:
>> 
>> Things were more spelled out:
>>         pkteng should be packetengines
>
>That sounds fine.  I will make the change.

What's next, directory naming by Windows-originating coding styles -
"Drivers/Networking/Ethernet/Packet Engines/"?

>> And things maybe not spelled out
>>         ixp2000 might just be ixp (what not intel?:)

I don't understand your logic of doing pkteng -> packetengines
and ixp2000 -> ixp at the same time. I was quite thankful that
Linux's driver names were not (always) TLAs like in OpenBSD.

>While this is an Intel chip, the part was sold off and the driver is not
>maintained by Intel.  That is reason why it does not reside in
>the /driver/net/ethernet/intel/ directory.

And that's why it probably should not be attempted. The i in ixp
will remind us enough that it once was Intel's doing - just as
in ixgb, rtl*, atl*, etc. Separation by company seems unnecessary
to me.
--
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