[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45a93e39-6530-fc1b-7808-51750691a470@gmail.com>
Date: Mon, 9 Oct 2017 12:40:15 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Tristram.Ha@...rochip.com, David.Laight@...LAB.COM
Cc: muvarov@...il.com, nathan.leigh.conrad@...il.com,
vivien.didelot@...oirfairelinux.com, UNGLinuxDriver@...rochip.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
andrew@...n.ch, pavel@....cz, ruediger.schmitt@...lips.com
Subject: Re: [PATCH v1 RFC 1/7] Replace license with GPL
On 10/09/2017 11:40 AM, Tristram.Ha@...rochip.com wrote:
>> From: Tristram.Ha@...rochip.com
>>> Sent: 06 October 2017 21:33
>>> Replace license with GPL.
>>
>> Don't you need permission from all the people who have updated
>> the files in order to make this change?
>>
>> David
>
> I am a little confused by your comment. The 4 original KSZ9477 DSA
> driver files were written by Woojung at Microchip Technology Inc.
> There was a complaint the "AS IS" license is not exactly GPL.
>
> It should be submitted formally to net-next instead of a RFC, but it
> is probably pointless to do that when there is no code change.
>
> I am hoping these drastic changes of KSZ9477 driver can be accepted
> so that the patches can be submitted formally to net-next.
What David is saying is that you need to take into account every one who
has been making changes to the Microchip driver, because anytime
someones submits a patch that gets accepted, their "voice" now counts:
Fortunately, the list seems to be fairly limited:
git shortlog -sne drivers/net/dsa/microchip
5 Arkadi Sharshevsky <arkadis@...lanox.com>
1 Woojung Huh <Woojung.Huh@...rochip.com>
So seeking contributor approval for a license change should be fairly
simple.
--
Florian
Powered by blists - more mailing lists