From: Thomas Hellstrom <thellstrom@vmware.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Alex Deucher <alexander.deucher@amd.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 3.19-rc1
Date: Tue, 16 Dec 2014 07:18:28 +0100 [thread overview]
Message-ID: <548FCEB4.6090109@vmware.com> (raw)
In-Reply-To: <CA+55aFzBS4p6NZcaggPmgOuRqnny4q+FcH6RM-5swJCw205JgA@mail.gmail.com>
On 12/16/2014 01:35 AM, Linus Torvalds wrote:
> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie <airlied@linux.ie> wrote:
>> i915:
>> Initial Skylake (SKL) support
>> gen3/4 reset work
>> start of dri1/ums removal
>> infoframe tracking
>> fixes for lots of things.
> So I'm not sure how happy I am about this. It seems to work, but on
> the very first boot I get this:
>
>
So this is my fault.
I posted the patch and there was a discussion with Chris Wilson at Intel
on dri-devel following the post concluding that the intel user-space
driver was type-casting dumb buffers, and that that was legitimate since
it didn't take place in generic user-space, but in a driver that had
detailed knowledge of the driver.
So I should have explicitly have withdrawn the patch. I'm sorry about this.
Thanks,
Thomas
next prev parent reply other threads:[~2014-12-16 6:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 7:17 [git pull] drm for 3.19-rc1 Dave Airlie
2014-12-16 0:35 ` Linus Torvalds
2014-12-16 0:48 ` Dave Airlie
2014-12-16 1:03 ` Linus Torvalds
2014-12-16 1:50 ` Dave Airlie
2014-12-16 2:15 ` Linus Torvalds
2014-12-16 2:37 ` Dave Airlie
2014-12-16 2:43 ` Linus Torvalds
2014-12-16 7:44 ` Chris Wilson
2014-12-16 1:48 ` Rob Clark
2014-12-16 6:18 ` Thomas Hellstrom [this message]
2014-12-16 6:32 ` Thomas Hellstrom
2014-12-16 8:16 ` Daniel Vetter
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=548FCEB4.6090109@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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