From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: tim.gardner@canonical.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MCP limit log messages, 2.6.36-rc4
Date: Fri, 24 Sep 2010 09:18:20 -0700 [thread overview]
Message-ID: <20100924091820.4f649786@jbarnes-desktop> (raw)
In-Reply-To: <4C9BD8D5.7080201@canonical.com>
On Fri, 24 Sep 2010 06:46:45 +0800
Tim Gardner <tim.gardner@canonical.com> wrote:
> Its just a debug hack which I wrote (that I mentioned in the first
> email) so I could figure out why the driver was complaining.
Oh sorry, missed that. An upstream patch for that would be welcome as
well.
> I'll be back from Asia by Monday and will give these patches a try.
Great, as I said you may still see spurious "over power" conditions,
but that's due to a bug in the i915 driver.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-09-24 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 17:47 Tim Gardner
2010-09-15 19:20 ` Tim Gardner
2010-09-16 12:49 ` Jesse Barnes
2010-09-23 20:48 ` Jesse Barnes
2010-09-23 21:54 ` Jesse Barnes
2010-09-23 22:46 ` Tim Gardner
2010-09-24 16:18 ` Jesse Barnes [this message]
2010-09-28 16:34 ` Tim Gardner
2010-09-28 17:18 ` Jesse Barnes
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=20100924091820.4f649786@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.com \
/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
Powered by JetHome