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:	Tue, 28 Feb 2012 20:58:13 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	rodrigue@....qualcomm.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	mcgrof@...jolero.org, qca-linux-team@...lcomm.com,
	nic-devel@...lcomm.com, kgiori@....qualcomm.com,
	chris.snook@...il.com, mathieu@....qualcomm.com,
	bryanh@...cinc.com, steventl@....qualcomm.com,
	hao-ran.liu@...onical.com, cjren@....qualcomm.com, joe@...ches.com
Subject: Re: [PATCH] net: add new QCA alx ethernet driver which supercedes
 atl1c

From: "Luis R. Rodriguez" <rodrigue@....qualcomm.com>
Date: Tue, 28 Feb 2012 17:50:10 -0800

> QCA is commiting on fixing all bugs upstream on this driver.

By implication QCA is not willing to fix bugs in and properly
maintain the existing in-tree atl1c driver.

We're not going to wholesale replace an entire driver in this
way, and you should know better Luis.

Please research the history of the Broadcom TG3 driver, Jeff Garzik
and myself wrote a driver for Linux ignoring Broadcom's out of tree
driver completely.

Several times Broadcom tried to just plunk their out-of-tree driver,
however properly cleaned up, into the tree.  We considerd that
unacceptable and pushed back until they started instead making gradual
improvements and fixes to the driver Jeff and myself wrote and had in
the tree already.  And they did.

We expect Qualcomm to follow this precedent, and I will push back
strongly on any attempt to just replace the existing driver.
--
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