From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Fu Michael <michael_fu@linux.intel.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Zhang Rui <rui.zhang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
lenb@kernel.org,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [Intel-gfx] [RFC] i915/acpi: add lid status notification and detection
Date: Fri, 22 May 2009 02:26:11 +0100 [thread overview]
Message-ID: <20090522012611.GA3136@srcf.ucam.org> (raw)
In-Reply-To: <4A15FE57.7040002@linux.intel.com>
On Fri, May 22, 2009 at 09:22:31AM +0800, Fu Michael wrote:
> Jesse Barnes wrote:
>> So is that two acks for the patch? If so, should it be split or can it
>> just go in through the i915 driver tree?
>>
>> Len? (Patch attached for reference.)
>>
>> Thanks,
>>
> Jesse, Just talked with Rui, the above status is based on "BIOS upgrade
> or FW fix is acceptable as a bug fix solution". are you ok with this? :)
> Many lid status has to be fixed via action such as DSDT upgrade...
Really? As I said, I'd be surprised if this is in any way common. What's
the exact problem description?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-05-22 1:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 18:57 [RFC] i915/acpi: add lid status notification and detection Jesse Barnes
2009-05-14 1:22 ` yakui_zhao
2009-05-15 18:16 ` [PATCH] " Jesse Barnes
2009-05-19 17:15 ` [RFC] " Matthew Garrett
2009-05-21 8:57 ` Zhang Rui
2009-05-21 16:34 ` Jesse Barnes
2009-05-22 1:22 ` [Intel-gfx] " Fu Michael
2009-05-22 1:26 ` Matthew Garrett [this message]
2009-05-22 2:03 ` Zhang Rui
2009-05-27 8:58 ` Jesse Barnes
2009-05-27 13:41 ` Fu Michael
2009-06-11 7:16 ` yakui_zhao
2009-06-16 18:33 ` Jesse Barnes
2009-06-16 19:08 ` Corentin Chary
2009-06-17 2:32 ` yakui_zhao
2009-06-17 23:10 ` Jesse Barnes
2009-07-07 22:51 ` Jesse Barnes
2009-06-18 15:49 ` Thomas Renninger
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=20090522012611.GA3136@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=michael_fu@linux.intel.com \
--cc=rui.zhang@intel.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 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.