From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC 43/72] a2065/ariadne: Move the a2065/ariadne drivers Date: Mon, 11 Jul 2011 07:31:28 -0400 Message-ID: <20110711113128.GA21187@infradead.org> References: <1309010363-22750-1-git-send-email-jeffrey.t.kirsher@intel.com> <1309010363-22750-44-git-send-email-jeffrey.t.kirsher@intel.com> <1310221836.26989.11.camel@jtkirshe-mobl> <1310345295.26989.76.camel@jtkirshe-mobl> <1310377198.26989.90.camel@jtkirshe-mobl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Geert Uytterhoeven , "davem@davemloft.net" , "netdev@vger.kernel.org" To: Jeff Kirsher Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:50025 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752978Ab1GKLbc (ORCPT ); Mon, 11 Jul 2011 07:31:32 -0400 Content-Disposition: inline In-Reply-To: <1310377198.26989.90.camel@jtkirshe-mobl> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Jul 11, 2011 at 02:39:57AM -0700, Jeff Kirsher wrote: > It may just be me, these statements seem negative and bitter and is not > helping us "solve" the issue. While the statements may be true, I > would like to try and find a solution, what ever it may be, to better > organize drivers/net/ethernet/ drivers to help with maintenance and > future development. It would help what the whole point of shuffling these drivers around in arbitrary ways is. Splitting them up for the actual protocols might make some sense, as would giving a subdirectory to every non-trivial driver. But what whole vendor split, even if consistently implemented seems like a lot of wanking for very little juice.