From: Keith Packard <keithp@keithp.com>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 2/2] drm/i915: drm/i915: Fix recursive calls to unmap
Date: Tue, 24 Jan 2012 15:00:56 -0800 [thread overview]
Message-ID: <86ipk0ln87.fsf@sumi.keithp.com> (raw)
In-Reply-To: <1327444923-13316-2-git-send-email-ben@bwidawsk.net>
[-- Attachment #1.1: Type: text/plain, Size: 396 bytes --]
On Tue, 24 Jan 2012 14:42:03 -0800, Ben Widawsky <ben@bwidawsk.net> wrote:
> This patch fixes gem_unref_active_buffers from i-g-t in the non-VTd
> case (ie. do_idle_maps forced to true).
Nice, one-line fix.
(if you agree with my <bikeshed> in the previous patch, this will have
to be changed to match)
Reviewed-by: Keith Packard <keithp@keithp.com>
--
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:[~2012-01-24 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 22:42 [PATCH 1/2] drm/i915: argument for deferring retirement Ben Widawsky
2012-01-24 22:42 ` [PATCH 2/2] drm/i915: drm/i915: Fix recursive calls to unmap Ben Widawsky
2012-01-24 23:00 ` Keith Packard [this message]
2012-01-25 4:02 ` Ben Widawsky
2012-01-25 15:50 ` Keith Packard
2012-01-24 23:00 ` [PATCH 1/2] drm/i915: argument for deferring retirement Keith Packard
2012-01-24 23:05 ` Eugeni Dodonov
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 4:36 [PATCH 0/2] infinite revusion patches v9999 Ben Widawsky
2012-01-25 4:36 ` [PATCH 2/2] drm/i915: drm/i915: Fix recursive calls to unmap Ben Widawsky
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=86ipk0ln87.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=ben@bwidawsk.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 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.