Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i915: reprogram power monitoring registers on resume
Date: Wed, 03 Nov 2010 21:48:13 +0000	[thread overview]
Message-ID: <5b55a1$iidall@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20101103202757.GJ8332@bombadil.infradead.org>

On Wed, 3 Nov 2010 16:27:57 -0400, Kyle McMartin <kyle@mcmartin.ca> wrote:
> From: Kyle McMartin <kyle@redhat.com>
> 
> Fixes issue where i915_gfx_val was reporting values several
> orders of magnitude higher than physically possible (without
> leaving scorch marks on my thighs at least.)

Applied to -fixes, thanks.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2010-11-03 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 20:27 [PATCH] i915: reprogram power monitoring registers on resume Kyle McMartin
2010-11-03 21:48 ` Chris Wilson [this message]

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='5b55a1$iidall@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.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