From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: ak@linux.intel.com, linux-acpi@vger.kernel.org,
linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Julia Jomantaite <julia.jomantaite@gmail.com>,
marcus@better.se, dannybaumann@web.de, corsac@debian.org
Subject: Re: [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware
Date: Thu, 3 Jul 2008 17:16:43 +0100 [thread overview]
Message-ID: <20080703161643.GB29110@srcf.ucam.org> (raw)
In-Reply-To: <200807031815.13291.trenn@suse.de>
On Thu, Jul 03, 2008 at 06:15:11PM +0200, Thomas Renninger wrote:
> On Thursday 03 July 2008 18:08:22 Matthew Garrett wrote:
> > On Thu, Jul 03, 2008 at 06:05:51PM +0200, Thomas Renninger wrote:
> > > Can these two go to linux-next or -mm, pls.
> >
> > Not until the opregion code is merged, no.
> Why?
Because it's entirely plausible that it'll break existing systems.
> Try the next patch, it works for the T61.
> These IGD parts could take quite a while still, while Toshibas and others
> remain broken (and T61 poke on wrong hardware which could cause
> all kind of badness).
The code's written and works, it just has a 750ms latency for reasons I
don't understand.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-07-03 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 16:05 [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware Thomas Renninger
2008-07-03 16:08 ` Matthew Garrett
2008-07-03 16:15 ` Thomas Renninger
2008-07-03 16:16 ` Matthew Garrett [this message]
2008-07-03 16:21 ` Yves-Alexis Perez
2008-07-03 19:24 ` Matthew Garrett
2008-07-04 10:08 ` Thomas Renninger
2008-07-04 10:18 ` Matthew Garrett
2008-07-04 3:09 ` Henrique de Moraes Holschuh
2008-07-04 9:13 ` Matthew Garrett
2008-07-04 11:55 ` Henrique de Moraes Holschuh
2008-07-04 17:39 ` Matthew Garrett
2008-07-04 19:49 ` Henrique de Moraes Holschuh
2008-07-05 15:46 ` Henrique de Moraes Holschuh
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=20080703161643.GB29110@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corsac@debian.org \
--cc=dannybaumann@web.de \
--cc=julia.jomantaite@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcus@better.se \
--cc=trenn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).