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] [day] [month] [year] [list]
Message-Id: <1154078800.3117.20.camel@laptopd505.fenrus.org>
Date:	Fri, 28 Jul 2006 11:26:40 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Jesse Huang <jesse@...lus.com.tw>
Cc:	Francois Romieu <romieu@...zoreil.com>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Andrew Morton <akpm@...l.org>, Jeff Garzik <jgarzik@...ox.com>
Subject: Re: Hello, We have IP100A Linux driver need to submit to 2.6.x
	kernel

On Fri, 2006-07-28 at 09:55 +0800, Jesse Huang wrote:
> Hi Francois:
> 
>     Sorry, I don't know this patch before. IP100A is a new version of IP100
> (sundance.c). I don't know what is you suggestion of IP100A driver? Should
> I...
> 
> 1. Only updata sundance.c to support IP100A
> 2. Release ip100a.c which support ip100(sundance) to kernel 2.6.x and ask to
> remove sundance.c.
> 3. Release ip100a.c with sundance.c both to kernel 2.6.x
> 
> We hope to use IP100a.c as our product driver, so 2. and 3. will better for
> IC Plus. But we will still follow your suggestion, if you feel 1. was better
> for kernel.


Hello,

in general the policy for Linux is that if adding support for a new
device is only minor changes to an existing driver, it is better to
update this existing driver with those changes. The reason for that is
that this makes it possible to share bugfixes and testing between both
devices. Now there is a point where it no longer makes sense to share,
for example when the devices are really very, very different. 

Greetings,
   Arjan van de Ven

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ