Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:53714 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754722Ab0JNSPL (ORCPT ); Thu, 14 Oct 2010 14:15:11 -0400 Date: Thu, 14 Oct 2010 14:14:47 -0400 From: "John W. Linville" To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Greg KH , =?iso-8859-1?Q?G=E1bor?= Stefanik , b43-dev , linux-wireless@vger.kernel.org, Henry Ptasinski , Brett Rudley , Nohee Ko Subject: Re: Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs) Message-ID: <20101014181446.GC2427@tuxdriver.com> References: <20101014165111.GA22130@suse.de> <20101014171739.GA28522@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Oct 14, 2010 at 07:38:49PM +0200, Rafał Miłecki wrote: > 2010/10/14 Greg KH : > > I don't think that bitfields are copyrightable :) > > What about rest of the code? brcm80211 seems to support even newer > devices we don't even try to support in b43 yet. > > Can I treat code as pure-GPL and do not care about that > maybe-not-GPL-compatible statement in header? IANAL, but I think you should include the copyright statment with a comment like "some portions covered by the following" at the top of the files including such code. Beyond that, I think you are fine including it under GPL terms (which are merely more restrictive, neither less restrictive nor incompatible). John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.