Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake.
Date: Mon, 08 Nov 2010 09:19:41 +0000	[thread overview]
Message-ID: <b9dded$h0pn1t@orsmga002.jf.intel.com> (raw)
In-Reply-To: <87d3qgdy80.fsf@pollan.anholt.net>

On Mon, 08 Nov 2010 00:19:11 -0800, Eric Anholt <eric@anholt.net> wrote:
> I'd rather not unless we find that it does really fix someone.

Moved to -next instead.
Thanks!
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2010-11-08  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06 21:53 [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake Eric Anholt
2010-11-06 21:53 ` [PATCH 2/2] drm/i915: Apply display workaround required according to the B-Spec Eric Anholt
2010-11-07 11:55   ` Chris Wilson
2010-11-06 22:07 ` [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake Chris Wilson
2010-11-08  8:19   ` Eric Anholt
2010-11-08  9:19     ` Chris Wilson [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='b9dded$h0pn1t@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=eric@anholt.net \
    --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