From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: forcewake warning fixes in debugfs
Date: Sun, 23 Oct 2011 13:25:45 -0700
Message-ID: <20111023132545.0fe5a4f5@bwidawsk.net>
References: <112133926.1639310.1317799673129.JavaMail.fmail@mwmweb012>
	<1317840294-6625-1-git-send-email-ben@bwidawsk.net>
	<20111008213215.GA2982@phenom.ffwll.local>
	<20111023101343.GD2953@phenom.ffwll.local>
	<yunaa8rbjjx.fsf@aiko.keithp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from cloud01.chad-versace.us (184-106-247-128.static.cloud-ips.com
	[184.106.247.128])
	by gabe.freedesktop.org (Postfix) with ESMTP id 795369E7B3
	for <intel-gfx@lists.freedesktop.org>;
	Sun, 23 Oct 2011 13:26:07 -0700 (PDT)
In-Reply-To: <yunaa8rbjjx.fsf@aiko.keithp.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Sun, 23 Oct 2011 12:21:38 -0700
Keith Packard <keithp@keithp.com> wrote:

> On Sun, 23 Oct 2011 12:13:43 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Hi Keith,
> > 
> > This patch isn't in your -next pull request. Please consider merging for
> > 3.2.
> 
> I didn't ever see a reply from Nicolas that it fixed his problem; would
> be nice to know whether this actually worked...
> 

I highly doubt it fixed his problem. The problem I was trying to fix was
to remove the spurious warnings we get, which was most likely the case
here. This patch does that correctly.

Ben