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]

Message-ID: <1308549708.13032.14.camel@Joe-Laptop>
Date:	Sun, 19 Jun 2011 23:01:48 -0700
From:	Joe Perches <joe@...ches.com>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	Jeff Kirsher <jeffrey.t.kirsher@...el.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 Mon, 2011-06-20 at 07:23 +0200, Jan Engelhardt wrote:
> 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?:)

Using embedded spaces is a poor choice.

> I don't understand your logic of doing pkteng -> packetengines

As demonstrated, it's too easy to typo
pkteng as pktgen.

> and ixp2000 -> ixp at the same time. I was quite thankful that
> Linux's driver names were not (always) TLAs like in OpenBSD.

The (what not intel?:) was just teasing.
I think ixp is sufficient.

I never thought of ixp2000 as the family
for the 2400 and 2800/2850.

Castine maybe, ixp2xxx maybe.
ixp2000?  Never heard of it.

Though maybe ixp would be confused for
those ixp4xx and maybe even the original
Digital/Intel ixp1200 parts too.

'course all of this is 10 years old now
and kind of pointless.

cheers, Joe

--
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