devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Bhuvanchandra DV
	<bhuvanchandra.dv-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>,
	Cory Tusar
	<cory.tusar-J6Z/VSE8EyIAspv4Qr0y0gC/G2K4zDHf@public.gmane.org>
Subject: Re: [PATCH 2/4] ARM: dts: vf610-colibri: relicense vf*colibri* under GPLv2/X11
Date: Wed, 25 Nov 2015 13:56:42 +0530	[thread overview]
Message-ID: <20151125082642.GB19921@Sanchayan-Arch.toradex.int> (raw)
In-Reply-To: <1448323278-23447-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>

On 15-11-23 16:01:18, Stefan Agner wrote:
> GPLv2-only devicetrees make reuse difficult for software components
> licensed under a different license.
> 
> The consensus is that a GPL/X11 dual-license should allow all necessary
> uses, so relicense the vf*colibri* files to this combination.

Acked-by: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-11-25  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24  0:01 [PATCH 2/4] ARM: dts: vf610-colibri: relicense vf*colibri* under GPLv2/X11 Stefan Agner
     [not found] ` <1448323278-23447-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-11-25  5:38   ` Cory Tusar
2015-11-25  8:26   ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w [this message]
2015-11-25  9:34 ` Bhuvanchandra DV

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=20151125082642.GB19921@Sanchayan-Arch.toradex.int \
    --to=maitysanchayan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bhuvanchandra.dv-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org \
    --cc=cory.tusar-J6Z/VSE8EyIAspv4Qr0y0gC/G2K4zDHf@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=stefan-XLVq0VzYD2Y@public.gmane.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).