From: "Bradley M. Kuhn" <bkuhn@ebb.org>
To: david@lang.hm
Cc: Pavel Machek <pavel@ucw.cz>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Greg KH <greg@kroah.com>, David Miller <davem@davemloft.net>,
"John W. Linville" <linville@tuxdriver.com>,
Stephen Hemminger <shemminger@vyatta.com>, "Perez-Gonzalez\,
Inaky" <inaky.perez-gonzalez@intel.com>,
Charles Marker <Charles.Marker@atheros.com>,
Jouni Malinen <Jouni.Malinen@atheros.com>,
Kevin Hayes <kevin@atheros.com>,
Zhifeng Cai <zhifeng.cai@atheros.com>,
Don Breslin <Don.Breslin@atheros.com>,
Doug Dahlby <Doug.Dahlby@atheros.com>,
Julia Lawall <julia@diku.dk>
Subject: Re: Challenges with doing hardware bring up with Linux first
Date: Wed, 01 Dec 2010 11:02:52 -0500 [thread overview]
Message-ID: <87hbex1nwz.fsf@ebb.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1011301209090.423@asgard.lang.hm> (david@lang.hm's message of "Tue, 30 Nov 2010 12:13:05 -0800 (PST)")
I assume someone started cc'ing me on this thread to get my opinion as a
non-lawyer GPL geek.
david@lang.hm wrote:
> However, there are quite a few files in the kernel that are BSD
> licensed, when combined with other GPL code, the only way you can
> re-distribute the result is under the GPL, so it is effectivly
> 'converted' when you compile, but by leaving the file BSD,
> improvements to it can be shared back with the original authors and
> put into their main codebase, so it's actually more polite to leave
> the license as-is for this file.
FWIW, I agree more or less completely with the above. I think the
implications are the same for ISC as well, as Luis points out elsewhere
in the thread.
--
-- bkuhn
next prev parent reply other threads:[~2010-12-01 16:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 8:46 Challenges with doing hardware bring up with Linux first Luis R. Rodriguez
2010-11-18 11:11 ` Theodore Tso
2010-11-18 16:46 ` Luis R. Rodriguez
2010-11-21 13:02 ` Ted Ts'o
2010-11-21 17:29 ` Greg KH
2010-11-21 19:51 ` Luis R. Rodriguez
2010-11-21 20:31 ` Alan Cox
2010-11-21 21:44 ` Ted Ts'o
2010-11-21 21:47 ` Gábor Stefanik
2010-11-21 21:50 ` Luis R. Rodriguez
2010-11-22 1:00 ` Greg KH
2010-11-21 23:35 ` Ted Ts'o
2010-11-21 21:49 ` Luis R. Rodriguez
2010-12-03 14:13 ` Pavel Machek
2010-11-21 21:47 ` Luis R. Rodriguez
2010-11-21 22:12 ` Luis R. Rodriguez
2010-11-18 11:34 ` Alan Cox
2010-11-18 16:51 ` Luis R. Rodriguez
2010-11-30 19:26 ` Pavel Machek
2010-11-30 19:30 ` Luis R. Rodriguez
2010-11-30 19:41 ` Luis R. Rodriguez
2010-11-30 20:00 ` Pavel Machek
2010-11-30 20:09 ` Luis R. Rodriguez
2010-11-30 20:13 ` david
2010-12-01 16:02 ` Bradley M. Kuhn [this message]
2010-11-18 16:45 ` Greg KH
2010-11-18 16:53 ` Luis R. Rodriguez
2010-11-18 17:23 ` Stephen Hemminger
2010-11-21 0:32 ` Adrian Chadd
2010-11-21 5:53 ` Luis R. Rodriguez
2010-11-21 7:11 ` Adrian Chadd
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=87hbex1nwz.fsf@ebb.org \
--to=bkuhn@ebb.org \
--cc=Charles.Marker@atheros.com \
--cc=Don.Breslin@atheros.com \
--cc=Doug.Dahlby@atheros.com \
--cc=Jouni.Malinen@atheros.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=david@lang.hm \
--cc=greg@kroah.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=julia@diku.dk \
--cc=kevin@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=pavel@ucw.cz \
--cc=shemminger@vyatta.com \
--cc=zhifeng.cai@atheros.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).