netdev - Re: [net-next RFC 6/7] i40evf: init code and hardware support

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, 27 Aug 2013 18:42:37 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
CC:	<davem@...emloft.net>,
	Mitch A Williams <mitch.a.williams@...el.com>,
	<netdev@...r.kernel.org>, <gospo@...hat.com>, <sassmann@...hat.com>
Subject: Re: [net-next RFC 6/7] i40evf: init code and hardware support

On Thu, 2013-08-22 at 21:53 -0700, Jeff Kirsher wrote:
[...]
> Intel does wish to maintain exclusive Copyright to these files, and will
> work with the community to implement requested changes or transfer
> Copyright for larger patches.  If you do see an issue with this code
> please email us and we will address any concerns in a timely manner.
[...]

I wonder why this is thought to be necessary.  I've never heard of
copyright assignment conditions being accepted in the Linux kernel.

Some Linux drivers are dual-licenced under a permissive licence and GPL,
and all contributions to them presumably also have to be dual-licenced.
It seems like that would allow you to retain the ability to reuse the
core hardware code on other operating systems and under proprietary
licences, even with copyrightable contributions from others.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
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