All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "K. Macy" <kmacy@freebsd.org>
Cc: Ed Maste <emaste@freebsdfoundation.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: FreeBSD i915 driver update
Date: Tue, 17 May 2016 10:20:28 +0300	[thread overview]
Message-ID: <87lh39dubn.fsf@intel.com> (raw)
In-Reply-To: <CAHM0Q_NZ7fUbXbiUskUkC2rNPr2Csa61MULuW_ezMGq7N0Cnew@mail.gmail.com>

On Fri, 13 May 2016, "K. Macy" <kmacy@freebsd.org> wrote:
> That would be much appreciated. I have the diff with upstream down to
> ~450 lines, so there likely isn't a whole lot that needs to change.
> However, there may be small things that are easier to do in the driver
> than in the linuxkpi.

Incidentally, there's some related discussion going on in dri-devel [1],
perhaps you'd like to chime in?

BR,
Jani.

[1] http://thread.gmane.org/gmane.comp.video.dri.devel/153947


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-05-17  7:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 21:12 FreeBSD i915 driver update Scott Long
2016-05-13  7:34 ` Jani Nikula
2016-05-13  7:43   ` K. Macy
2016-05-17  7:20     ` Jani Nikula [this message]
2016-05-17  7:38       ` K. Macy
2016-05-13  8:39   ` Scott Long
2016-05-13 14:00   ` Ed Maste
2016-05-17 10:23   ` Daniel Vetter
2016-05-17 15:09     ` K. Macy
2016-05-18  8:11       ` Daniel Vetter
2016-05-18  8:50         ` K. Macy
2016-05-18  1:10     ` randyf
  -- strict thread matches above, loose matches on Subject: below --
2016-05-12 20:18 Scott Long
2016-05-13 13:27 ` Jani Nikula

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=87lh39dubn.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=emaste@freebsdfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kmacy@freebsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.