dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Kevin Brace <kevinbrace@gmx.com>
Cc: Dave Airlie <airlied@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: It appears drm-next TTM cleanup broke something . . .
Date: Sun, 18 Oct 2020 23:04:12 +0200	[thread overview]
Message-ID: <20201018210412.GA515543@ravnborg.org> (raw)
In-Reply-To: <trinity-7bf82d9f-a022-48f3-bca0-d06eb28ebe35-1603048517864@3c-app-mailcom-bs08>

Hi Kevin.

On Sun, Oct 18, 2020 at 09:15:17PM +0200, Kevin Brace wrote:
> As usual, I pulled in DRM repository code for an out of tree OpenChrome DRM repository a few days ago.

I know you have been working on and off on the openchrome driver for a
long time now. Any chance we will see the driver submitted for upstream soon?

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-10-18 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18 19:15 It appears drm-next TTM cleanup broke something . . Kevin Brace
2020-10-18 19:50 ` Dave Airlie
2020-10-19  7:23   ` Kevin Brace
2020-10-19 10:13     ` Christian König
2020-10-19 16:20       ` Kevin Brace
2020-10-19 16:37         ` Christian König
2020-10-18 21:04 ` Sam Ravnborg [this message]
2020-10-19 19:43   ` Kevin Brace
2020-10-19 20:28     ` Sam Ravnborg
2020-10-20  6:45       ` Thomas Zimmermann
2020-10-20  9:30         ` Sam Ravnborg
2020-10-20 17:17     ` Alex Deucher
2020-10-20 18:03       ` Ilia Mirkin
2020-10-21  8:03     ` Thomas Zimmermann
2020-10-21  8:14       ` Daniel Vetter
2020-10-21  8:30         ` Thomas Zimmermann

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=20201018210412.GA515543@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kevinbrace@gmx.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