From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755143Ab2DGAgZ (ORCPT ); Fri, 6 Apr 2012 20:36:25 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:50554 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752446Ab2DGAgY (ORCPT ); Fri, 6 Apr 2012 20:36:24 -0400 MIME-Version: 1.0 In-Reply-To: <1333757482-16204-1-git-send-email-mcgrof@frijolero.org> References: <1333757482-16204-1-git-send-email-mcgrof@frijolero.org> From: Linus Torvalds Date: Fri, 6 Apr 2012 17:36:03 -0700 X-Google-Sender-Auth: piFW34MA_Gnd06Vp68B0X_OX84w Message-ID: Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK To: "Luis R. Rodriguez" Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org, Keith Packard , Ralf Baechle , David Woodhouse , Stephen Hemminger , "John W. Linville" , Greg Kroah-Hartman Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 6, 2012 at 5:11 PM, Luis R. Rodriguez wrote: > -MODULE_LICENSE("Dual BSD/GPL"); > +MODULE_LICENSE("GPL-Compatible"); I really don't see the point. This makes things *worse*. "Dual BSD/GPL" actually tells you something: it tells you that you can take that code, and use it in a BSD project. In contrast "GPL-compatible" tells you nothing at all. So you are actually removing real information, and just making things harder for everybody. Linus