From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, intel-gfx@lists.freedesktop.org
Subject: Re: Possible i915 regression with 4.4-rc
Date: Fri, 04 Dec 2015 10:44:17 +0200 [thread overview]
Message-ID: <8737vi1u3i.fsf@intel.com> (raw)
In-Reply-To: <20151203213559.GA29847@nuc-i3427.alporthouse.com>
On Thu, 03 Dec 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, Dec 03, 2015 at 11:25:48PM +0200, Ville Syrjälä wrote:
>> I think we had some bug with not properly pinning the fbdev buffer which
>> could explain things getting corrupted. Chris had a fix I think, but I'm
>> not sure if that went anywhere. Chris?
>
> Jani keeps refusing it :)
Which one? Was I being a boring pedant, requiring it gets review or
compiles or something...? :p
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-04 8:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 20:00 Possible i915 regression with 4.4-rc Takashi Iwai
2015-12-03 20:33 ` Ville Syrjälä
2015-12-03 21:08 ` Takashi Iwai
2015-12-03 21:25 ` Ville Syrjälä
2015-12-03 21:35 ` Chris Wilson
2015-12-04 8:44 ` Jani Nikula [this message]
2015-12-04 15:57 ` Daniel Vetter
2015-12-04 12:00 ` Dave Gordon
2015-12-04 12:06 ` Chris Wilson
2015-12-04 12:16 ` Chris Wilson
2015-12-04 12:45 ` Chris Wilson
2015-12-03 21:38 ` Lukas Wunner
2015-12-08 7:03 ` Takashi Iwai
2015-12-04 8:49 ` Jani Nikula
2015-12-04 9:40 ` Ville Syrjälä
2015-12-04 16:02 ` Daniel Vetter
2015-12-04 16:12 ` Takashi Iwai
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=8737vi1u3i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
--cc=ville.syrjala@linux.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