[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <024c01c6b6a0$fcf783e0$4964a8c0@icplus.com.tw>
Date: Thu, 3 Aug 2006 10:03:17 +0800
From: "Jesse Huang" <jesse@...lus.com.tw>
To: "Jeff Garzik" <jgarzik@...ox.com>
Cc: "John W. Linville" <linville@...driver.com>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<akpm@...l.org>, "Francois Romieu" <romieu@...zoreil.com>
Subject: Re: [PATCH] Create IP100A Driver
Dear Jeff:
I had discuss with our peoples. We decided to use sundance.c to support
IP100A. We will also update some bug fix to this driver.
Thanks for your suggestion.
Best Regards,
Jesse Huang
----- Original Message -----
From: "Jeff Garzik" <jgarzik@...ox.com>
To: "Jesse Huang" <jesse@...lus.com.tw>
Cc: "John W. Linville" <linville@...driver.com>;
<linux-kernel@...r.kernel.org>; <netdev@...r.kernel.org>; <akpm@...l.org>
Sent: Friday, July 28, 2006 6:14 PM
Subject: Re: [PATCH] Create IP100A Driver
Although it is occasionally OK to duplicate a driver, I do not see a
compelling case with ip100a.
The stronger case for a single codebase is won on the strengths of lower
long-term maintenance costs, increased strength of review, doesn't break
existing sundance driver uses, and re-use of existing testing benefits.
If you feel strongly about not showing "sundance" to your users, you can
always submit a one-line MODULE_ALIAS() change which permits users to
load "ip100a" (really sundance.c). Using MODULE_ALIAS() seems quite
reasonable, given that IC Plus appears to be taking the lead in future
Sundance-like chip development.
So, please resubmit as changes to the existing sundance.c. This is
better for the standard Linux kernel engineering process.
Thanks,
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists