From: Luis R. Rodriguez <mcgrof@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>, "Greg KH" <gregkh@suse.de>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org,
"Henry Ptasinski" <henryp@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Nohee Ko" <noheek@broadcom.com>
Subject: Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs)
Date: Thu, 14 Oct 2010 11:18:59 -0700 [thread overview]
Message-ID: <AANLkTinf_uZMhYk-AVBRyprOp=AW0GEkqVEzfYsiFmXa@mail.gmail.com> (raw)
In-Reply-To: <20101014181446.GC2427@tuxdriver.com>
On Thu, Oct 14, 2010 at 11:14 AM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Thu, Oct 14, 2010 at 07:38:49PM +0200, Rafa? Mi?ecki wrote:
>> 2010/10/14 Greg KH <gregkh@suse.de>:
>
>> > 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).
Agreed, for an example of where this was done check the ar9170 driver,
Johannes took ISC licensed code from Otus and GPL'd it. You really can
only GPL the code if you are making copyrightable changes to it though
so best is if you leave the header as-is with the existing license
unless you are making tons of changes. For further details you can
refer to these guidelines:
http://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
Luis
prev parent reply other threads:[~2010-10-14 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 16:40 Licensing wlc_phy_radio.h and brcm80211 (was: [PATCH 3/3] b43: N-PHY: add 2055 radio regs) Rafał Miłecki
[not found] ` <20101014165111.GA22130@suse.de>
2010-10-14 17:06 ` Rafał Miłecki
[not found] ` <20101014171739.GA28522@suse.de>
2010-10-14 17:24 ` Michael Büsch
2010-10-14 17:38 ` Rafał Miłecki
2010-10-14 18:14 ` John W. Linville
2010-10-14 18:18 ` Luis R. Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinf_uZMhYk-AVBRyprOp=AW0GEkqVEzfYsiFmXa@mail.gmail.com' \
--to=mcgrof@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=brudley@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--cc=noheek@broadcom.com \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).