netdev - Re: [PATCH 0/15] RFC: create drivers/net/legacy for ISA, EISA, MCA drivers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1288316896.1836.41.camel@Joe-Laptop>
Date:	Thu, 28 Oct 2010 18:48:16 -0700
From:	Joe Perches <joe@...ches.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: [PATCH 0/15] RFC: create drivers/net/legacy for ISA, EISA, MCA
 drivers

On Thu, 2010-10-28 at 21:19 -0400, Paul Gortmaker wrote:
> The drivers/net dir has a lot of files - originally there were
> no subdirs, but at least now subdirs are being used effectively.
> But the original drivers from 10+ years ago are still right
> there at the top.  This series creates a drivers/net/legacy dir.

Hi Paul.

I like this idea.

I suggest a bit of a further grouping by using a
drivers/net/ethernet directory and putting those
legacy drivers in a new subdirectory
drivers/net/ethernet/legacy.

> The initial target is things like ISA/EISA/MCA drivers, and with
> that alone, we can get close to 90 files out of drivers/net.
> Plus, by having a semi-defined description for legacy as being
> "drivers more than 10 years old" we'll always have a destination
> for drivers as they fall out of maintainership and use.

I think legacy is "old and not sold or used much anymore".

I believe you're not moving 3c59x as that's relatively
still popular even though it's nearly 15 years old.

Or maybe that was just an oversight...



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