From: Keith Packard <keithp@keithp.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: drm/i915: Fix recursive calls to unmap
Date: Wed, 25 Jan 2012 07:50:38 -0800 [thread overview]
Message-ID: <86k44feq7l.fsf@sumi.keithp.com> (raw)
In-Reply-To: <4F1F7EEF.2010603@bwidawsk.net>
[-- Attachment #1.1: Type: text/plain, Size: 437 bytes --]
On Tue, 24 Jan 2012 20:02:55 -0800, Ben Widawsky <ben@bwidawsk.net> wrote:
> I agree with the bikeshed, however I am not sure what you expect changed
> here. do_idle_maps is still forced to true to test the fix. So I'm going
> to assume you just read the comment too quickly and resubmit with the
> updated patches.
Just that the boolean sense of the new parameter is reversed, nothing else.
--
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-25 15:50 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
2012-01-25 4:02 ` Ben Widawsky
2012-01-25 15:50 ` Keith Packard [this message]
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=86k44feq7l.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.