linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: igep: Relicense the IGEP boards under GPLv2/X11
Date: Thu, 7 Jun 2018 23:32:22 -0700	[thread overview]
Message-ID: <20180608063222.GL5738@atomide.com> (raw)
In-Reply-To: <20180606152500.14034-1-enric.balletbo@collabora.com>

Hi,

* Enric Balletbo i Serra <enric.balletbo@collabora.com> [180606 08:27]:
> The current GPLv2 only licensing on IGEP boards makes it very impractical
> for other software components licensed under another license.
> 
> In order to make it easier for them to reuse our device trees, relicense
> all boards under a GPLv2/X11 dual-license. Also switch to use the SPDX
> identifiers and remove the boiler plate license text.

I don't think you have all the people in Cc who have already
contributed patches to these files, can you please check the
files with git log?

Regards,

Tony

  reply	other threads:[~2018-06-08  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 15:24 [PATCH 1/2] ARM: dts: igep: Relicense the IGEP boards under GPLv2/X11 Enric Balletbo i Serra
2018-06-08  6:32 ` Tony Lindgren [this message]
2018-06-08  6:41   ` Tony Lindgren

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=20180608063222.GL5738@atomide.com \
    --to=tony@atomide.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 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).