From: Alan Cox <alan@linux.intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Matthew Garrett <mjg@redhat.com>,
linux-acpi@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: Use generic IGD opregion code for gma500
Date: Thu, 3 Mar 2011 11:43:58 +0000 [thread overview]
Message-ID: <20110303114358.1300bacd@bob.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1103022115120.12344@x980>
On Wed, 02 Mar 2011 21:16:28 -0500 (EST)
Len Brown <lenb@kernel.org> wrote:
> i mean to say that 1/2 was applied to acpi-test, rather than 2/2.
Oh ok - thats fine then - I don't know if the IGD opregion code is
busted somewhere or the GMA500 patch but if the GMA bit isn't applied
and the rest works on i9xx all is fine
next prev parent reply other threads:[~2011-03-03 12:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 20:03 [PATCH 1/2] ACPI/Intel: Rework Opregion support Matthew Garrett
2011-02-22 20:03 ` [PATCH 2/2] staging: Use generic IGD opregion code for gma500 Matthew Garrett
2011-02-22 21:15 ` Alan Cox
2011-03-03 2:14 ` Len Brown
2011-03-03 2:16 ` Len Brown
2011-03-03 11:43 ` Alan Cox [this message]
2011-03-03 11:43 ` Alan Cox
2011-03-03 13:07 ` Matthew Garrett
2011-03-03 12:52 ` Alan Cox
2011-02-22 20:18 ` [Intel-gfx] [PATCH 1/2] ACPI/Intel: Rework Opregion support Jesse Barnes
2011-03-03 2:14 ` Len Brown
2011-03-14 17:59 ` [PATCH] " Chris Wilson
2011-03-15 1:18 ` Indan Zupancic
2011-03-15 1:52 ` Matthew Garrett
2011-03-15 13:30 ` [Intel-gfx] " Olivier Galibert
2011-03-15 13:32 ` Matthew Garrett
2011-03-15 13:40 ` Olivier Galibert
2011-03-15 13:43 ` Matthew Garrett
2011-03-15 8:37 ` Chris Wilson
2011-03-15 11:13 ` Indan Zupancic
2011-03-15 11:27 ` Peter Stuge
2011-03-15 11:46 ` Indan Zupancic
2011-03-15 16:06 ` Alex Deucher
2011-03-16 0:02 ` Indan Zupancic
2011-03-16 2:17 ` Alex Deucher
2011-03-16 6:26 ` Indan Zupancic
2011-03-16 14:11 ` Jerome Glisse
2011-03-16 3:46 ` Dave Airlie
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=20110303114358.1300bacd@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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