From: Heiko Stuebner <heiko@sntech.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Klaus Goger <klaus.goger@theobroma-systems.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Huibin Hong <huibin.hong@rock-chips.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Kever Yang <kever.yang@rock-chips.com>,
LKML <linux-kernel@vger.kernel.org>,
Joseph Chen <chenjh@rock-chips.com>,
Romain Perier <romain.perier@collabora.com>,
Matthias Kaehlcke <mka@chromium.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Sugar Zhang <sugar.zhang@rock-chips.com>,
Simon Xue <xxm@rock-chips.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Brian Norris <briannorris@chromium.org>,
Russell King <linux@armlinux.org.uk>,
Ja
Subject: Re: [PATCH 0/2] Use SPDX-License-Identifier for rockchip devicetree files
Date: Mon, 04 Jun 2018 12:18:13 +0200 [thread overview]
Message-ID: <1726970.J2eQlPlkUj@phil> (raw)
In-Reply-To: <CAD=FV=WA44n8MYtGZTQN3r0F86E=xDcdWhQDLDOkyqS=aaCXfQ@mail.gmail.com>
Am Freitag, 15. Dezember 2017, 18:29:02 CEST schrieb Doug Anderson:
> Hi,
>
> On Fri, Dec 15, 2017 at 3:44 AM, Klaus Goger
> <klaus.goger@theobroma-systems.com> wrote:
> > This patch series replaces all the license text in rockchip devicetree
> > files text with a proper SPDX-License-Identifier.
> > It follows the guidelines submitted[1] by Thomas Gleixner that are not
> > yet merged.
> >
> > These series also fixes the issue with contradicting statements in most
> > licenses. The introduction text claims to be GPL or X11[2] but the
> > following verbatim copy of the license is actually a MIT[3] license.
> > The X11 license includes a advertise clause and trademark information
> > related to the X Consortium. As these X Consortium specfic points are
> > irrelevant for us we stick with the actuall license text.
> >
> > [1] https://patchwork.kernel.org/patch/10091607/
> > [2] https://spdx.org/licenses/X11.html
> > [3] https://spdx.org/licenses/MIT.html
> >
> >
> > Klaus Goger (2):
> > arm64: dts: rockchip: use SPDX-License-Identifier
> > ARM: dts: rockchip: use SPDX-License-Identifier
> >
> > arch/arm/boot/dts/rk3036-evb.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3036-kylin.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3036.dtsi | 40 +---------------------
> > arch/arm/boot/dts/rk3066a-bqcurie2.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3066a-marsboard.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3066a-mk808.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3066a-rayeager.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3066a.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3188-px3-evb.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3188-radxarock.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3188.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3228-evb.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3229-evb.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3229.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk322x.dtsi | 40 +---------------------
> > arch/arm/boot/dts/rk3288-evb-act8846.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3288-evb-rk808.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3288-evb.dtsi | 40 +---------------------
> > arch/arm/boot/dts/rk3288-fennec.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3288-firefly-beta.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-firefly-reload.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-firefly.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-firefly.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-miqi.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-phycore-rdk.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-phycore-som.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-popmetal.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-r89.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-rock2-som.dtsi | 40 +---------------------
> > arch/arm/boot/dts/rk3288-rock2-square.dts | 40 +---------------------
> > arch/arm/boot/dts/rk3288-tinker.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-analog-audio.dtsi | 5 +--
> > arch/arm/boot/dts/rk3288-veyron-brain.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-jaq.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-jerry.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-mickey.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-minnie.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-pinky.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-sdmmc.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron-speedy.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288-veyron.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rk3288-vyasa.dts | 39 +--------------------
> > arch/arm/boot/dts/rk3288.dtsi | 40 +---------------------
> > arch/arm/boot/dts/rk3xxx.dtsi | 39 +--------------------
> > arch/arm/boot/dts/rv1108-evb.dts | 40 +---------------------
> > arch/arm/boot/dts/rv1108.dtsi | 40 +---------------------
> > arch/arm64/boot/dts/rockchip/rk3328-evb.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3328.dtsi | 39 +--------------------
> > .../arm64/boot/dts/rockchip/rk3368-evb-act8846.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 39 +--------------------
> > .../boot/dts/rockchip/rk3368-orion-r68-meta.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3368.dtsi | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 39 +--------------------
> > .../arm64/boot/dts/rockchip/rk3399-puma-haikou.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 39 +--------------------
> > .../dts/rockchip/rk3399-sapphire-excavator.dts | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi | 39 +--------------------
> > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 39 +--------------------
> > 69 files changed, 69 insertions(+), 2603 deletions(-)
>
> This is just removing the verbatim license text and adding a link to
> another file with the text? ...and correcting the name of the
> alternate license to be the MIT license... I'm no lawyer, but if
> that's what everyone in the kernel agrees is the way they want it
> going forward then I have no objections to anything I was involved in.
correct.
Documentation/process/license-rules.rst Describes the process of
handling these license identifiers.
There was one criticism in the beginning, that an arbitary third-party
site would hold the binding license texts, but that got resolved by
including LICENSES/preferred/$identifier into the kernel sources itself.
Heiko
next prev parent reply other threads:[~2018-06-04 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:44 [PATCH 0/2] Use SPDX-License-Identifier for rockchip devicetree files Klaus Goger
[not found] ` <20171215114427.32059-1-klaus.goger-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
2017-12-15 11:44 ` [PATCH 1/2] arm64: dts: rockchip: use SPDX-License-Identifier Klaus Goger
2017-12-15 11:44 ` [PATCH 2/2] ARM: " Klaus Goger
2017-12-15 13:45 ` [PATCH 0/2] Use SPDX-License-Identifier for rockchip devicetree files Philippe Ombredanne
2017-12-15 14:28 ` Heiko Stübner
2017-12-15 14:42 ` Philippe Ombredanne
[not found] ` <CAOFm3uHuwmU1nCcU1MQ9qgGZ0A70ycuoo8XpWcDzgPQFzFRnRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-15 15:20 ` Heiko Stübner
2017-12-15 16:27 ` klaus.goger
2017-12-15 19:19 ` Brian Norris
[not found] ` <24788EB1-9868-41E9-B97C-7D85D8C3761D-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
2017-12-18 11:43 ` Matthias Brugger
2017-12-15 17:29 ` Doug Anderson
2018-06-04 10:18 ` Heiko Stuebner [this message]
2018-06-04 10:19 ` Heiko Stuebner
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=1726970.J2eQlPlkUj@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=chenjh@rock-chips.com \
--cc=dianders@chromium.org \
--cc=huibin.hong@rock-chips.com \
--cc=kernel@esmil.dk \
--cc=kever.yang@rock-chips.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=romain.perier@collabora.com \
--cc=sugar.zhang@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=xxm@rock-chips.com \
--cc=xypron.glpk@gmx.de \
/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).