From: David Brown <davidb@codeaurora.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Brown <davidb@codeaurora.org>,
Daniel Walker <dwalker@codeaurora.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Abhijeet Dharmapurikar <adharmap@codeaurora.org>,
Gregory Bean <gbean@codeaurora.org>,
Stepan Moskovchenko <stepanm@codeaurora.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 05/25] msm: generalize clock support.
Date: Fri, 28 May 2010 10:56:13 -0700 [thread overview]
Message-ID: <20100528175613.GA5455@huya.qualcomm.com> (raw)
In-Reply-To: <20100527153413.GC1957@elf.ucw.cz>
On Thu, May 27, 2010 at 05:34:14PM +0200, Pavel Machek wrote:
> > > Are you sure? I believe that Dual GPL/BSD is ok, just BSD is not.
> >
> > It is, according to the FSF
> > <http://www.gnu.org/licenses/license-list.html>
>
> Not acording to kernel sources. Please make it dual GPL/BSD.
If this is actually necessary, we can go back and wrangle another
license change, but it is a fairly painful and unpleasant
process.
We changed to this license initially because of an objection to
a dual license (admittedly a poorly worded one).
The BSD license is compatible with the GPL, and it should not be
necessary to add any kind of dual license to it.
David
next prev parent reply other threads:[~2010-05-28 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 21:45 [PATCH 05/25] msm: generalize clock support Daniel Walker
2010-05-24 18:55 ` Pavel Machek
2010-05-24 19:20 ` dwalker
2010-05-25 0:51 ` David Brown
2010-05-26 17:37 ` Pavel Machek
2010-05-26 18:58 ` David Brown
2010-05-27 15:34 ` Pavel Machek
2010-05-28 17:56 ` David Brown [this message]
2010-05-29 13:51 ` Jamie Lokier
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=20100528175613.GA5455@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=adharmap@codeaurora.org \
--cc=dwalker@codeaurora.org \
--cc=gbean@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stepanm@codeaurora.org \
/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).