From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, stable@kernel.org
Subject: Re: [PATCH 1/3] drm/i915: Ivybridge still has fences!
Date: Thu, 03 Nov 2011 09:23:18 -0700 [thread overview]
Message-ID: <yun39e5rx8p.fsf@aiko.keithp.com> (raw)
In-Reply-To: <aefc95$1v47nd@orsmga001.jf.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 373 bytes --]
On Sun, 23 Oct 2011 13:35:45 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sun, 23 Oct 2011 14:09:07 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Keith, can take a look at patches 1-2 and consider merging them for 3.2?
>
> Those two are
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
And merged to -next.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 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-11-03 16:23 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 ` [PATCH 1/3] drm/i915: Ivybridge still has fences! Jesse Barnes
2011-10-23 10:12 ` 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 [this message]
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=yun39e5rx8p.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.