[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1309024963.2454.85.camel@jtkirshe-mobl>
Date: Sat, 25 Jun 2011 11:02:42 -0700
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Sriram <srk@...com>, Vinay Hegde <vinay.hegde@...com>,
Cyril Chemparathy <cyril@...com>,
Wan ZongShun <mcuos.com@...il.com>,
Lennert Buytenhek <kernel@...tstofly.org>,
Krzysztof Halasa <khc@...waw.pl>,
Anant Gole <anantgole@...com>,
Chaithrika U S <chaithrika@...com>
Subject: Re: [RFC 26/72] arm: Move the ARM/ACORN drivers
On Sat, 2011-06-25 at 09:59 -0700, Arnd Bergmann wrote:
>
> > ether1 is 82586, so presumably that should be Intel subdirectory.
>
> Yes, according to the new layout, it should at least live together
> with the other 82586-based drivers (eexpress.c, ni52.c, sun3_82586.c),
> which could be either a directory for all of these, or the
> generic intel directory.
My personal preference is that these drivers that were not created by
Intel or maintained by Intel, not be in the Intel sub-directory.
While many of the drivers were organized in a layout that matches
drivers/net/ethernet/<company>, I tried to organize the drivers in the
most logical way possible (i.e. 8390/ all the drivers that used the 8390
shared files).
I do like all the suggestions made, except for the suggestion to move
eexpress.c, eepro.c, sun3_82596.c, etc. in to the intel sub-directory.
I am open to suggestions on a way to better to organize these drivers
that use an Intel part but were created and maintained by someone else.
Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)
Powered by blists - more mailing lists