linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Use SPDX-License-Identifier for rockchip devicetree files
Date: Fri, 15 Dec 2017 15:28:34 +0100	[thread overview]
Message-ID: <21020918.S4038j3A1a@diego> (raw)
In-Reply-To: <CAOFm3uHba4kBD81thpxSpDBsDS4Y5m7cN2jfYt_uT5atdSDmqg@mail.gmail.com>

Am Freitag, 15. Dezember 2017, 14:45:34 CET schrieb Philippe Ombredanne:
> Klaus,
> 
> On Fri, Dec 15, 2017 at 12:44 PM, 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
> 
> FWIW, the X11 license name was not always something clearly defined.
> SPDX calls it clearly MIT which is the most widely accepted name for
> the corresponding text. And this is also what we have in Thomas doc
> patches that should be the kernel reference.
> 
> Also, as a general note, you want to make sure that such as patch set
> is not merged by mistake until you have collected an explicit review
> or ack from all the copyright holders involved.

Just for my understanding, is it really necessary to get Acks from _all_
previous contributors?

I see that Thomas patches moving license texts into the kernel itself do not 
seem to have landed yet, but when the actual license text does _not_ change
and only its location to a common place inside the kernel sources, it feels
a bit overkill trying to get Acks from _everybody_ that contributed to
Rockchip devicetrees for the last 4 years.

If we would actually want to change the license I would definitly feel 
differently, but the license text does not change.


Thanks
Heiko

  reply	other threads:[~2017-12-15 14:28 UTC|newest]

Thread overview: 12+ 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
2017-12-15 11:44 ` [PATCH 1/2] arm64: dts: rockchip: use SPDX-License-Identifier 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 [this message]
2017-12-15 14:42     ` Philippe Ombredanne
2017-12-15 15:20       ` Heiko Stübner
2017-12-15 16:27         ` klaus.goger at theobroma-systems.com
2017-12-15 19:19           ` Brian Norris
2017-12-18 11:43           ` Matthias Brugger
2017-12-15 17:29 ` Doug Anderson
2018-06-04 10:18   ` Heiko Stuebner
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=21020918.S4038j3A1a@diego \
    --to=heiko@sntech.de \
    --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).