From: Emmanuel Vadot <manu@bidouilliste.com>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: daniel.vetter@ffwll.ch, coypu@sdf.org, dri-devel@lists.freedesktop.org
Subject: Re: drm core/helpers and MIT license
Date: Sat, 16 Nov 2019 12:57:15 +0100 [thread overview]
Message-ID: <20191116125715.0e83ce339c421465fa00266e@bidouilliste.com> (raw)
In-Reply-To: <f6629560-6b95-c125-a1d5-51554b2a1dab@tronnes.org>
On Fri, 15 Nov 2019 15:33:46 +0100
Noralf Trønnes <noralf@tronnes.org> wrote:
>
>
> Den 15.11.2019 13.34, skrev Ville Syrjälä:
> > On Thu, Nov 14, 2019 at 08:01:32PM +0000, coypu@sdf.org wrote:
> >> Hi Daniel,
> >>
> >> I don't think we can make any complaints about GPL being more widely
> >> used in the DRM code. It's nice to have the code at all, the MIT license
> >> is a bonus. Thanks for writing it and bearing with us.
> >>
> >> Would rewrites done purely for licensing reasons be accepted upstream?
> >
> > Rewrite should be the last resort. I think a lot of the GPL only stuff
> > is quite recent so there's a good chance the author(s) are still around
> > to discuss relicensing.
> >
>
> If someone sends patches to MIT license the work I've done, I'll be
> happy to ack it. It's only recently that I've been aware of the fact
> that MIT licensed was a thing in the kernel. I was under the impression
> that all new code should be GPL and MIT were for code imported from
> elsewhere. I would love to see my work being used on the BSD's.
And I would love to be able to use your work on FreeBSD :)
I don't really know the rules but shouldn't you send a patch to
relicence ?
Right now for me drm_client (and others) being GPL is a problem for my
update of DRM in FreeBSD so I'm not using it (which is bad and will
probably cause problems).
> Noralf.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Emmanuel Vadot <manu@bidouilliste.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-16 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 20:01 drm core/helpers and MIT license coypu
2019-11-15 9:06 ` Daniel Vetter
2019-11-15 12:34 ` Ville Syrjälä
2019-11-15 14:33 ` Noralf Trønnes
2019-11-16 11:57 ` Emmanuel Vadot [this message]
2019-11-16 13:37 ` Noralf Trønnes
2019-11-18 15:22 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 15:03 Daniel Vetter
2019-11-14 8:43 ` Simon Ser
[not found] ` <CAKMK7uH-8+tbKsAoiChsxELEc_77RVVxP2wapHWhqB+0Viifog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-15 15:38 ` Alex Deucher
2019-11-15 15:38 ` Alex Deucher
2019-11-16 12:12 ` Emmanuel Vadot
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=20191116125715.0e83ce339c421465fa00266e@bidouilliste.com \
--to=manu@bidouilliste.com \
--cc=coypu@sdf.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=noralf@tronnes.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).