From: Rob Landley <rob@landley.net>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: Rob Herring <robherring2@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Device Tree Blob (DTB) licence
Date: Mon, 25 May 2015 02:14:28 -0500 [thread overview]
Message-ID: <CAOS_Y6Q37ps+VEnzUZ_uwX++qrRm9Hgx45Q_pmiZSLSNjmKwZg@mail.gmail.com> (raw)
In-Reply-To: <1432322832.5304.63.camel@opteya.com>
On Fri, May 22, 2015 at 2:27 PM, Yann Droneaud <ydroneaud@opteya.com> wrote:
> I've added licensing@fsf.ogrg in Cc: in my previous message to have an
> advice on this subject, but I failed to notice licensing@fsf.org
> is not a mailing list: I was assigned request ID [gnu.org #1017262].
>
> Regards.
They're also not an unbiased source. Their job is to reply "you should
license it under GPLv3" without actually looking at your message.
(This is a slight oversimplification, they may instead recomend the
GFDL. They will never _not_ recommend one of their licenses.)
Personally, I'm sad we're starting to get ACPI for arm but if device
tree data files are only available under GPL, people will hold their
nose and deploy ACPI.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: rob@landley.net (Rob Landley)
To: linux-arm-kernel@lists.infradead.org
Subject: Device Tree Blob (DTB) licence
Date: Mon, 25 May 2015 02:14:28 -0500 [thread overview]
Message-ID: <CAOS_Y6Q37ps+VEnzUZ_uwX++qrRm9Hgx45Q_pmiZSLSNjmKwZg@mail.gmail.com> (raw)
In-Reply-To: <1432322832.5304.63.camel@opteya.com>
On Fri, May 22, 2015 at 2:27 PM, Yann Droneaud <ydroneaud@opteya.com> wrote:
> I've added licensing at fsf.ogrg in Cc: in my previous message to have an
> advice on this subject, but I failed to notice licensing at fsf.org
> is not a mailing list: I was assigned request ID [gnu.org #1017262].
>
> Regards.
They're also not an unbiased source. Their job is to reply "you should
license it under GPLv3" without actually looking at your message.
(This is a slight oversimplification, they may instead recomend the
GFDL. They will never _not_ recommend one of their licenses.)
Personally, I'm sad we're starting to get ACPI for arm but if device
tree data files are only available under GPL, people will hold their
nose and deploy ACPI.
Rob
next prev parent reply other threads:[~2015-05-25 7:14 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 10:05 Device Tree Blob (DTB) licence Yann Droneaud
2015-05-05 10:05 ` Yann Droneaud
2015-05-05 10:05 ` Yann Droneaud
2015-05-05 16:41 ` Rob Herring
2015-05-05 16:41 ` Rob Herring
2015-05-05 16:41 ` Rob Herring
2015-05-22 10:05 ` Yann Droneaud
2015-05-22 10:05 ` Yann Droneaud
2015-05-22 10:05 ` Yann Droneaud
2015-05-22 16:26 ` Rob Herring
2015-05-22 16:26 ` Rob Herring
2015-05-22 16:26 ` Rob Herring
2015-05-28 12:31 ` Enrico Weigelt, metux IT consult
2015-05-28 12:31 ` Enrico Weigelt, metux IT consult
2015-05-28 12:31 ` Enrico Weigelt, metux IT consult
2015-05-22 19:27 ` Yann Droneaud
2015-05-22 19:27 ` Yann Droneaud
2015-05-22 19:27 ` Yann Droneaud
2015-05-25 7:14 ` Rob Landley [this message]
2015-05-25 7:14 ` Rob Landley
2015-05-25 7:14 ` Rob Landley
2015-05-25 20:04 ` Willy Tarreau
2015-05-25 20:04 ` Willy Tarreau
2015-05-25 20:04 ` Willy Tarreau
2015-05-28 12:32 ` Enrico Weigelt, metux IT consult
2015-05-28 12:32 ` Enrico Weigelt, metux IT consult
2015-05-28 12:32 ` Enrico Weigelt, metux IT consult
2015-05-28 13:34 ` Russell King - ARM Linux
2015-05-28 13:34 ` Russell King - ARM Linux
2015-05-28 13:34 ` Russell King - ARM Linux
2015-05-28 16:52 ` Enrico Weigelt, metux IT consult
2015-05-28 16:52 ` Enrico Weigelt, metux IT consult
2015-05-28 16:52 ` Enrico Weigelt, metux IT consult
2015-05-29 6:47 ` Willy Tarreau
2015-05-29 6:47 ` Willy Tarreau
2015-05-29 6:47 ` Willy Tarreau
2015-05-29 11:35 ` Enrico Weigelt, metux IT consult
2015-05-29 11:35 ` Enrico Weigelt, metux IT consult
2015-05-29 11:35 ` Enrico Weigelt, metux IT consult
2015-05-29 22:16 ` David Lang
2015-05-29 22:16 ` David Lang
2015-05-29 22:16 ` David Lang
2015-05-30 15:28 ` Geert Uytterhoeven
2015-05-30 15:28 ` Geert Uytterhoeven
2015-05-30 15:28 ` Geert Uytterhoeven
2015-06-01 13:12 ` One Thousand Gnomes
2015-06-01 13:12 ` One Thousand Gnomes
2015-06-01 13:12 ` One Thousand Gnomes
2015-06-01 15:19 ` Warner Losh
2015-06-01 15:19 ` Warner Losh
2015-05-29 3:31 ` Rob Landley
2015-05-29 3:31 ` Rob Landley
2015-05-29 3:31 ` Rob Landley
2015-05-29 15:10 ` Enrico Weigelt, metux IT consult
2015-05-29 15:10 ` Enrico Weigelt, metux IT consult
2015-05-29 15:10 ` Enrico Weigelt, metux IT consult
2015-05-29 22:21 ` David Lang
2015-05-29 22:21 ` David Lang
2015-05-29 22:21 ` David Lang
2015-05-30 2:43 ` Jean-Christophe PLAGNIOL-VILLARD
2015-05-30 2:43 ` Jean-Christophe PLAGNIOL-VILLARD
2015-05-30 2:43 ` Jean-Christophe PLAGNIOL-VILLARD
2015-06-22 12:57 ` Pavel Machek
2015-06-22 12:57 ` Pavel Machek
2015-06-22 12:57 ` Pavel Machek
2015-05-30 19:59 ` Jeroen Hofstee
2015-05-30 19:59 ` Jeroen Hofstee
2015-05-30 19:59 ` Jeroen Hofstee
2015-05-31 7:12 ` Warner Losh
2015-05-31 7:12 ` Warner Losh
2015-05-31 7:12 ` Warner Losh
2015-06-01 13:17 ` One Thousand Gnomes
2015-06-01 13:17 ` One Thousand Gnomes
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=CAOS_Y6Q37ps+VEnzUZ_uwX++qrRm9Hgx45Q_pmiZSLSNjmKwZg@mail.gmail.com \
--to=rob@landley.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=ydroneaud@opteya.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.