All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts
Date: Sun, 3 Aug 2014 15:04:30 +0200	[thread overview]
Message-ID: <20140803130430.GY3952@lukather> (raw)
In-Reply-To: <20140731192016.GA6869@excalibur.cnev.de>

Hi,

On Thu, Jul 31, 2014 at 09:20:16PM +0200, Karsten Merker wrote:
> Hello,
> 
> I have today read the patch by Hans de Goede to add a dts file
> for the "Banana Pi" development board (see
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/276339.html)
> and have stumbled over the license declaration at the beginning:
> 
> > +/*
> > + * Copyright 2014 Hans de Goede <hdegoede@redhat.com>
> > + *
> > + * The code contained herein is licensed under the GNU General Public
> > + * License. You may obtain a copy of the GNU General Public License
> > + * Version 2 or later at the following locations:
> > + *
> > + * http://www.opensource.org/licenses/gpl-license.html
> > + * http://www.gnu.org/copyleft/gpl.html
> > + */
> 
> The phrase "The code contained herein is licensed under the GNU
> General Public License" does not make explicitly clear under
> which version(s) of the GPL the code can be used.  From the
> following "You may obtain a copy of the GNU General Public
> License Version 2 or later at the following locations [...]" one
> can deduce that the intention is most probably to license the
> code unter GPL2+, but from a legal point of view this information
> should be an explicit part of the license statement itself, as
> strictly formally speaking the latter statement does only inform
> the reader where he can find the text of GPL2 and later GPL
> versions, but does not expressly apply them to the code.  This is
> of course a rather formalistic view and may well be seen as
> beancounting, but I have seen too many cases where formal license
> ambiguities have led to problems years later, so I proposed to
> Hans to change the wording in his patch to something more
> explicit, similar to the dts files for other arm platforms.
> 
> A phrasing like used in the GPL appendix ("This program is
> free software; you can redistribute it and/or modify it under the
> terms of the GNU General Public License as published by the Free
> Software Foundation; either version 2 of the License, or (at your
> option) any later version") would avoid any ambiguity.
> 
> Hans agreed that the current phrasing is not ideal and should
> probably be changed to something unabiguous but pointed out that a
> similar wording is used in all the other dts files for Allwinner
> SOCs (arch/arm/boot/dts/sun?i-a*.dts) and proposed to refer the
> issue to you as the Allwinner platform maintainer (with the
> linux-arm-kernel and devicetree lists in CC).

Thanks for reporting this.

>From a quick grep, the issue is actually broader than just
Allwinner. At least the following platforms seem to do the same:
  - mvebu
  - axm5516
  - bcm
  - berlin
  - ea3250
  - ecx-2000
  - highbank
  - imx / mxs
  - lpc32xx
  - phy3250
  - picoxcell
  - shmobile
  - rockchip
  - socfpga
  - spear
  - ste
  - zynq

Would you mind sending a patch to fix all these?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140803/34b07625/attachment-0001.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Karsten Merker <merker-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts
Date: Sun, 3 Aug 2014 15:04:30 +0200	[thread overview]
Message-ID: <20140803130430.GY3952@lukather> (raw)
In-Reply-To: <20140731192016.GA6869-Hlt6eto4P0pdWf7zwHaZWbNAH6kLmebB@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3109 bytes --]

Hi,

On Thu, Jul 31, 2014 at 09:20:16PM +0200, Karsten Merker wrote:
> Hello,
> 
> I have today read the patch by Hans de Goede to add a dts file
> for the "Banana Pi" development board (see
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/276339.html)
> and have stumbled over the license declaration at the beginning:
> 
> > +/*
> > + * Copyright 2014 Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > + *
> > + * The code contained herein is licensed under the GNU General Public
> > + * License. You may obtain a copy of the GNU General Public License
> > + * Version 2 or later at the following locations:
> > + *
> > + * http://www.opensource.org/licenses/gpl-license.html
> > + * http://www.gnu.org/copyleft/gpl.html
> > + */
> 
> The phrase "The code contained herein is licensed under the GNU
> General Public License" does not make explicitly clear under
> which version(s) of the GPL the code can be used.  From the
> following "You may obtain a copy of the GNU General Public
> License Version 2 or later at the following locations [...]" one
> can deduce that the intention is most probably to license the
> code unter GPL2+, but from a legal point of view this information
> should be an explicit part of the license statement itself, as
> strictly formally speaking the latter statement does only inform
> the reader where he can find the text of GPL2 and later GPL
> versions, but does not expressly apply them to the code.  This is
> of course a rather formalistic view and may well be seen as
> beancounting, but I have seen too many cases where formal license
> ambiguities have led to problems years later, so I proposed to
> Hans to change the wording in his patch to something more
> explicit, similar to the dts files for other arm platforms.
> 
> A phrasing like used in the GPL appendix ("This program is
> free software; you can redistribute it and/or modify it under the
> terms of the GNU General Public License as published by the Free
> Software Foundation; either version 2 of the License, or (at your
> option) any later version") would avoid any ambiguity.
> 
> Hans agreed that the current phrasing is not ideal and should
> probably be changed to something unabiguous but pointed out that a
> similar wording is used in all the other dts files for Allwinner
> SOCs (arch/arm/boot/dts/sun?i-a*.dts) and proposed to refer the
> issue to you as the Allwinner platform maintainer (with the
> linux-arm-kernel and devicetree lists in CC).

Thanks for reporting this.

From a quick grep, the issue is actually broader than just
Allwinner. At least the following platforms seem to do the same:
  - mvebu
  - axm5516
  - bcm
  - berlin
  - ea3250
  - ecx-2000
  - highbank
  - imx / mxs
  - lpc32xx
  - phy3250
  - picoxcell
  - shmobile
  - rockchip
  - socfpga
  - spear
  - ste
  - zynq

Would you mind sending a patch to fix all these?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-03 13:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 19:20 Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts Karsten Merker
2014-07-31 19:20 ` Karsten Merker
2014-08-03 13:04 ` Maxime Ripard [this message]
2014-08-03 13:04   ` Maxime Ripard
2014-08-03 17:59   ` Arnd Bergmann
2014-08-03 17:59     ` Arnd Bergmann
2014-08-04 19:25     ` Maxime Ripard
2014-08-04 19:25       ` Maxime Ripard
2014-08-04 21:23       ` Russell King - ARM Linux
2014-08-04 21:23         ` Russell King - ARM Linux
2014-08-05  8:06         ` Arnd Bergmann
2014-08-05  8:06           ` Arnd Bergmann
2014-08-07 13:20         ` Maxime Ripard
2014-08-07 13:20           ` Maxime Ripard
2014-09-02 10:22           ` Maxime Ripard
2014-09-02 10:22             ` Maxime Ripard
2014-09-02 10:40             ` Russell King - ARM Linux
2014-09-02 10:40               ` Russell King - ARM Linux
2014-09-02 11:54               ` Chen-Yu Tsai
2014-09-02 11:54                 ` Chen-Yu Tsai
2014-09-02 12:27               ` Maxime Ripard
2014-09-02 12:27                 ` Maxime Ripard
2014-09-02 12:35                 ` Hans de Goede
2014-09-02 12:35                   ` Hans de Goede
2014-09-02 12:51                   ` Maxime Ripard
2014-09-02 12:51                     ` Maxime Ripard
2014-09-02 13:02                     ` Arnd Bergmann
2014-09-02 13:02                       ` Arnd Bergmann
2014-09-02 13:37                     ` Russell King - ARM Linux
2014-09-02 13:37                       ` Russell King - ARM Linux
2014-09-02 16:52                       ` Russell King - ARM Linux
2014-09-02 16:52                         ` Russell King - ARM Linux
2014-09-02 14:42                     ` Hans de Goede
2014-09-02 14:42                       ` Hans de Goede
2014-09-02 15:18                       ` Maxime Ripard
2014-09-02 15:18                         ` Maxime Ripard
2014-09-02 16:24                       ` Russell King - ARM Linux
2014-09-02 16:24                         ` Russell King - ARM Linux
2014-08-05  8:01       ` Hans de Goede
2014-08-05  8:01         ` Hans de Goede
2014-08-05  8:02       ` Hans de Goede
2014-08-05  8:02         ` Hans de Goede
2014-08-03 20:41   ` Russell King - ARM Linux
2014-08-03 20:41     ` Russell King - ARM Linux

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=20140803130430.GY3952@lukather \
    --to=maxime.ripard@free-electrons.com \
    --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 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.