dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: change i915_sw_fence license to MIT
Date: Tue, 20 Nov 2018 09:31:22 +1100	[thread overview]
Message-ID: <20181119223122.GA20916@largo.jsg.id.au> (raw)
In-Reply-To: <20181119180930.GD19415@intel.com>

On Mon, Nov 19, 2018 at 10:09:33AM -0800, Rodrigo Vivi wrote:
> On Sun, Nov 18, 2018 at 08:44:30PM +1100, Jonathan Gray wrote:
> > On Wed, Oct 31, 2018 at 08:43:03AM +0000, Chris Wilson wrote:
> > > Quoting Jonathan Gray (2018-10-31 00:56:12)
> > > > Chris Wilson said Intel is willing to change the license of these files
> > > > to MIT.
> > > > 
> > > > Signed-off-by: Jonathan Gray <jsg@jsg.id.au>
> > > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > -Chris
> > 
> > Still looking to get this merged/reviewed by one of the i915 maintainers.
> 
> I believe this patch should have a better commit message.

It isn't clear what should be changed, what do you have in mind?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-11-19 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  0:56 [PATCH] drm/i915: change i915_sw_fence license to MIT Jonathan Gray
2018-10-31  8:43 ` Chris Wilson
2018-11-18  9:44   ` Jonathan Gray
2018-11-19 18:09     ` Rodrigo Vivi
2018-11-19 22:31       ` Jonathan Gray [this message]
2018-11-23 10:14         ` Joonas Lahtinen
2018-11-23 12:28           ` Jonathan Gray
2018-11-23 13:01             ` Joonas Lahtinen
2018-11-23 14:53               ` Jonathan Gray
2018-11-28 17:44                 ` Joonas Lahtinen

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=20181119223122.GA20916@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@intel.com \
    /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