netdev - Re: [RFC 02/72] 3c*/acenic/typhoon: Move 3Com Ethernet 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 09 Jul 2011 08:27:43 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Philip Blundell <philb@....org>,
	Steffen Klassert <klassert@...hematik.tu-chemnitz.de>,
	David Dillow <dave@...dillows.org>,
	Jes Sorensen <jes@...ined-monkey.org>,
	Donald Becker <becker@...ld.com>,
	Craig Southeren <craigs@...luki.apana.org.au>,
	David Hinds <dahinds@...rs.sourceforge.net>
Subject: Re: [RFC 02/72] 3c*/acenic/typhoon: Move 3Com Ethernet drivers

On Tue, 2011-06-28 at 01:22 -0700, Alan Cox wrote:
> On Sat, 25 Jun 2011 06:58:13 -0700
> Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
> 
> > Moves the 3Com drivers into drivers/net/ethernet/3com/ and the
> > necessary Kconfig and Makefile changes.
> 
> This seems a bizarre way to carve stuff up.
> 
> To start with several of the things you put in 3com are just branded
> items, or are boards using non 3com devices which are currently with
> the other drivers that do so, some even use shared midlayers that you
> move them away from.

When I first started the process of organizing drivers/net/ I thought it
made sense to group the 3Com drivers together, even though one of the
drivers (3c503) used the 8390 common code.  Looking back, it does make
sense to keep the 3c503 driver in drivers/net/ethernet/8390/ along with
the other 8390 drivers.

> 
> You also pull stuff out of pcmcia which makes it harder to scan stuff
> grouped logically.

The logic behind this was to have all the Ethernet drivers in
drivers/net/ethernet/.  Since the drivers in drivers/net/pcmcia/ are not
sharing any special network common code or library, it did not seem to
make sense to me to keep them in drivers/net/pcmcia.  Eventually, there
would not be a drivers/net/pcmcia directory since all the drivers in
that directory would be moved into the appropriate
drivers/net/<technology>/ directory (i.e. ethernet, token-ring,fddi,
wireless, etc).  If there were a number of PCMCIA Ethernet drivers,
which all shared a common library or code, then it would make sense to
place them in drivers/net/ethernet/pcmcia/

> So this all seems a bit daft to me.
> 
> Surely it would make sense to put all the Intel 825xx stuff together,
> all the 8390 stuff together and so on.
> 
> Alan

Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)