From: Matthew Garrett <mjg@redhat.com>
To: Alan Cox <alan@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>,
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 13:07:24 +0000 [thread overview]
Message-ID: <20110303130724.GB22181@srcf.ucam.org> (raw)
In-Reply-To: <20110303114306.31114533@bob.linux.org.uk>
On Thu, Mar 03, 2011 at 11:43:06AM +0000, Alan Cox wrote:
> On Wed, 02 Mar 2011 21:14:31 -0500 (EST)
> Len Brown <lenb@kernel.org> wrote:
>
> > applied to acpi-test
>
> NAK this - with it applied the GMA500 driver oopses in the opregion code
Awesome. Got a backtrace? I'm kind of lacking in hardware (and no, this
is not a plea for some gma500)
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-03-03 13:07 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
2011-03-03 11:43 ` Alan Cox
2011-03-03 13:07 ` Matthew Garrett [this message]
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=20110303130724.GB22181@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=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 \
/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