From: Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/nouveau: fix bogus GPL-2 license header
Date: Fri, 21 Jun 2019 19:10:26 +0100 [thread overview]
Message-ID: <20190621181026.GG21486@arch-x1c3> (raw)
In-Reply-To: <20190620001343.11046-1-imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
On 2019/06/19, Ilia Mirkin wrote:
> The bulk SPDX addition made all these files into GPL-2.0 licensed files.
> However the remainder of the project is MIT-licensed, these files
> (primarily header files) were simply missing the boiler plate and got
> caught up in the global update.
>
> Fixes: b24413180f5 (License cleanup: add SPDX GPL-2.0 license identifier to files with no license)
> Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
> ---
>
> Ben, you did like 99.7% of this work, so ultimately your call. Pretty
> much all of these were split out from other MIT-licensed files, and most
> are header files anyways.
>
All of my glorious 23 patches to nouveau are meant to be under MIT.
Acked-by: Emil Velikov <emil.l.velikov@gmail.com>
> Another change might be to add the SPDX identifier to files *with*
> the MIT boilerplate, but I didn't want to do too much here.
>
No objections on my end :-)
-Emil
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2019-06-21 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 0:13 [PATCH] drm/nouveau: fix bogus GPL-2 license header Ilia Mirkin
[not found] ` <20190620001343.11046-1-imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2019-06-21 18:10 ` Emil Velikov [this message]
2019-06-22 18:10 ` [Nouveau] " Karol Herbst
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=20190621181026.GG21486@arch-x1c3 \
--to=emil.l.velikov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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