From: Jiri Slaby <jslaby@suse.cz>
To: daniel@ffwll.ch
Cc: Keith Packard <keithp@keithp.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Jiri Slaby <jirislaby@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: g33: tiled output
Date: Thu, 01 Dec 2011 19:55:28 +0100 [thread overview]
Message-ID: <4ED7CDA0.4030609@suse.cz> (raw)
In-Reply-To: <20111201162231.GB4291@phenom.ffwll.local>
On 12/01/2011 05:22 PM, Daniel Vetter wrote:
> Something is pretty decently broken here. Can you please file a bug at
> freedesktop.org against the i915 drm?
Just for reference if someone is reading this later:
https://bugs.freedesktop.org/show_bug.cgi?id=43427
thanks,
--
js
suse labs
prev parent reply other threads:[~2011-12-01 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 14:37 g33: tiled output Jiri Slaby
2011-12-01 15:42 ` Daniel Vetter
2011-12-01 15:49 ` Jiri Slaby
2011-12-01 16:01 ` Jiri Slaby
2011-12-01 16:22 ` Daniel Vetter
2011-12-01 18:55 ` Jiri Slaby [this message]
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=4ED7CDA0.4030609@suse.cz \
--to=jslaby@suse.cz \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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