netdev - RE: [PATCH] net: add QCA alx Ethernet driver

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:	Wed, 29 Feb 2012 07:30:20 +0000
From:	"Huang, Xiong" <xiong@....qualcomm.com>
To:	David Miller <davem@...emloft.net>
CC:	"Rodriguez, Luis" <rodrigue@....qualcomm.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	qca-linux-team <qca-linux-team@...lcomm.com>,
	nic-devel <nic-devel@...lcomm.com>,
	"Giori, Kathy" <kgiori@....qualcomm.com>,
	"chris.snook@...il.com" <chris.snook@...il.com>
Subject: RE: [PATCH] net: add QCA alx Ethernet driver

My another concern is the license type. Current atl1c use GPL v2, and got some contribution outside of QCA though the first version 
was wrote by our Atheros guy. And that guy just copied the license from atl1e/atl1x that contains the words "Derived from Intel e1000".

If I update this driver and add new chip support on it, Our Company's legal might not permit me to do so, they prefer QCA ISC license.
Is it possible to change the license header to ISC while I applying patches to source code ?


Thanks
xiong

> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Wednesday, February 29, 2012 11:33
> To: Huang, Xiong
> Cc: Rodriguez, Luis; netdev@...r.kernel.org; linux-kernel@...r.kernel.org;
> qca-linux-team; nic-devel; Giori, Kathy; chris.snook@...il.com; Olivari,
> Mathieu; Huntsman, Bryan
> Subject: Re: [PATCH] net: add QCA alx Ethernet driver
> 
> From: "Huang, Xiong" <xiong@....qualcomm.com>
> Date: Wed, 29 Feb 2012 03:11:14 +0000
> 
> > We understand your concern.  To support the new chipset, do you think
> > it's reasonable to upstream it as a new driver, not a replacement ?
> 
> It depends upon how similar the chips are.
> 
> To be honest tg3, as one example, supports quite a large array of different
> pieces of hardware that use the same logical core.
> 
> So that would be my litmus test about how different a chip needs to be to
> deserve an entirely new driver.
> 
> I strongly suggest you try to get atl1c working properly.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html