From: John W. Linville <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "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 14:14:47 -0400 [thread overview]
Message-ID: <20101014181446.GC2427@tuxdriver.com> (raw)
In-Reply-To: <AANLkTimz7xKtz15tVyytxgJ3mQJUNk-=ja-4cJBWJUV8@mail.gmail.com>
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).
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-10-14 18:14 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 [this message]
2010-10-14 18:18 ` Luis R. Rodriguez
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=20101014181446.GC2427@tuxdriver.com \
--to=linville@tuxdriver.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=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).