From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Sun, 14 Sep 2008 18:27:25 -0400 From: Steven Toth In-reply-to: <48CD8A4B.4090209@linuxtv.org> To: Andreas Oberritter Message-id: <48CD8FCD.7010201@linuxtv.org> MIME-version: 1.0 References: <564277.58085.qm@web46102.mail.sp1.yahoo.com> <48CD41BD.8040508@linuxtv.org> <48CD88CF.7060601@linuxtv.org> <48CD8A4B.4090209@linuxtv.org> Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Multiproto API/Driver Update List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: Andreas Oberritter wrote: > Steven Toth wrote: >> Markus Rechberger wrote: >>> Great move Steven! Can we move the TDA10048 code over, maybe adding >>> a note that it's dual licensed would be nice? >> In principle yes. >> >> I'd like to see an example of dual license just to make sure it has no >> nasty side effects. >> >> Can you point me at one of your dual-license drivers so I can review the >> wording? > > AFAIK the biggest problem with dual licensing is that you cannot merge > patches from Linus' tree, because they are not dual licensed (unless, of > course, you'll get the permission from the contributors). That's also been my understanding in the past. As the copyright owner I'm legally entitled to generate a separate license for the code I originally merged into Linus's tree, though - correct? (Perhaps not any updates that were subsequently made to that code by the community). I guess this is would be seen legally as two pieces of code with two distinct licenses, not a dual license... or maybe I'm splitting hairs. Regardless, it will be an interest exercise to review the proposed dual license, even if nothing good can come from it. - Steve _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb