From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, stable@kernel.org
Subject: Re: [PATCH 1/3] drm/i915: Ivybridge still has fences!
Date: Mon, 10 Oct 2011 10:58:22 -0700 [thread overview]
Message-ID: <20111010105822.58114c0e@jbarnes-desktop> (raw)
In-Reply-To: <1318189923-4609-1-git-send-email-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 330 bytes --]
On Sun, 9 Oct 2011 21:52:01 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> So don't forget to restore them on resume and dump them into
> the error state.
This should probably just be >= 6 instead; I don't think we're getting
rid of fences anytime soon.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 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-10-10 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 19:52 [PATCH 1/3] drm/i915: Ivybridge still has fences! Daniel Vetter
2011-10-09 19:52 ` [PATCH 2/3] drm/i915: add constants to size fence arrays and fields Daniel Vetter
2011-10-09 19:54 ` Daniel Vetter
2011-10-09 19:52 ` [PATCH 3/3] drm/i915: enable support for 32 fences on ivybridge Daniel Vetter
2011-10-10 17:58 ` Jesse Barnes [this message]
2011-10-23 10:12 ` [PATCH 1/3] drm/i915: Ivybridge still has fences! Daniel Vetter
2011-10-23 10:18 ` Jesse Barnes
2011-10-23 11:23 ` Chris Wilson
2011-10-23 12:09 ` Daniel Vetter
2011-10-23 12:35 ` Chris Wilson
2011-11-03 16:23 ` Keith Packard
2011-10-23 20:45 ` Kenneth Graunke
2011-10-23 22: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=20111010105822.58114c0e@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@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