From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/25] msm: generalize clock support.
Date: Wed, 26 May 2010 19:37:54 +0200 [thread overview]
Message-ID: <20100526173753.GD9069@elf.ucw.cz> (raw)
In-Reply-To: <20100525005115.GA7791@huya.qualcomm.com>
On Tue 2010-05-25 00:51:15, David Brown wrote:
> On Mon, May 24, 2010 at 11:55:40AM -0700, Pavel Machek wrote:
>
> > > + * Redistribution and use in source and binary forms, with or without
> > > + * modification, are permitted provided that the following conditions are
> > > + * met:
> >
> > Is this even GPL compatible?
>
> 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.
pavel at amd:/data/l/linux-good$ less ./include/linux/license.h
#ifndef __LICENSE_H
#define __LICENSE_H
static inline int license_is_gpl_compatible(const char *license)
{
return (strcmp(license, "GPL") == 0
|| strcmp(license, "GPL v2") == 0
|| strcmp(license, "GPL and additional rights") == 0
|| strcmp(license, "Dual BSD/GPL") == 0
|| strcmp(license, "Dual MIT/GPL") == 0
|| strcmp(license, "Dual MPL/GPL") == 0);
}
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-05-26 17:37 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 at codeaurora.org
2010-05-25 0:51 ` David Brown
2010-05-26 17:37 ` Pavel Machek [this message]
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
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=20100526173753.GD9069@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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).