From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: i915 fixes
Date: Wed, 13 Apr 2011 09:30:01 -0700 [thread overview]
Message-ID: <yunwriynmgm.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1302683305-19417-1-git-send-email-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 522 bytes --]
On Wed, 13 Apr 2011 09:28:22 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> At the moment, only the first patch ("drm/i915: Initialise g4x watermarks for
> disabled pipe") looks ready. Keith, I think this reflects the consensus
> we reached for that particular patch; I have the second stage of
> unifying the identical ironlake/g4x routines pending for -next.
Yup. I've merged that to my drm-intel-fixes branch.
Do we have any other regression fixes pending for .39?
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-04-13 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 8:28 i915 fixes Chris Wilson
2011-04-13 8:28 ` [PATCH 1/3] drm/i915: Initialise g4x watermarks for disabled pipes Chris Wilson
2011-04-13 8:28 ` [PATCH 2/3] drm/i915: Move the irq wait queue initialisation into the ring init Chris Wilson
2011-04-14 6:20 ` Ben Widawsky
2011-04-14 6:58 ` Chris Wilson
2011-04-13 8:28 ` [PATCH 3/3] drm/i915: Disable all outputs early, before KMS takeover Chris Wilson
2011-04-14 6:23 ` Ben Widawsky
2011-04-13 16:30 ` Keith Packard [this message]
2011-04-13 16:49 ` i915 fixes Chris Wilson
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=yunwriynmgm.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).