From: Jamie Lokier <jamie@shareable.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: Sat, 29 May 2010 14:51:30 +0100 [thread overview]
Message-ID: <20100529135130.GC3106@shareable.org> (raw)
In-Reply-To: <20100527153413.GC1957@elf.ucw.cz>
Pavel Machek wrote:
> On Wed 2010-05-26 18:58:33, David Brown wrote:
> > On Wed, May 26, 2010 at 07:37:54PM +0200, Pavel Machek wrote:
> >
> > > > Um, this is a standard 3-clause BSD license. There are nearly
> > > > 900 existing files in the kernel that have this license on them.
> > >
> > > 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.
Glibc contains many source files with only a BSD license header, and
various other GPL-compatible licenses.
If it's fine for Glibc, I believe it is surely fine for Linux.
Pavel, do you mean something specific by "not according to kernel sources"?
-- Jamie
prev parent reply other threads:[~2010-05-29 13:51 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
2010-05-29 13:51 ` Jamie Lokier [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=20100529135130.GC3106@shareable.org \
--to=jamie@shareable.org \
--cc=adharmap@codeaurora.org \
--cc=davidb@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).