From: Daniel Vetter <daniel@ffwll.ch>
To: coypu@sdf.org
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org
Subject: Re: drm core/helpers and MIT license
Date: Fri, 15 Nov 2019 10:06:29 +0100 [thread overview]
Message-ID: <20191115090629.GA23790@phenom.ffwll.local> (raw)
In-Reply-To: <20191114200132.GA11077@SDF.ORG>
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?
Figuring that out is why I started this thread. Thus far the consensus
seems to be a deafening *shrug*, so no idea.
Personally I'm happy to take any patches with a clear net benefit in terms
of contributions/hw support/maintenability for linux gpu support.
Everything else probably needs a much wider support in the community.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
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-15 9:06 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 [this message]
2019-11-15 12:34 ` Ville Syrjälä
2019-11-15 14:33 ` Noralf Trønnes
2019-11-16 11:57 ` Emmanuel Vadot
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=20191115090629.GA23790@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=coypu@sdf.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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).