From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org, Bastien Nocera <hadess@hadess.net>
Subject: Re: [git pull] Input updates for 2.6.34-rc6
Date: Fri, 14 May 2010 16:38:42 +0100 [thread overview]
Message-ID: <20100514153842.GA6398@srcf.ucam.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1005140751300.3711@i5.linux-foundation.org>
On Fri, May 14, 2010 at 07:54:53AM -0700, Linus Torvalds wrote:
> But the issue here is that on a "legacy PC", we can't just say "ACPI
> doesn't mention this device, so it can't exist". Because in a legacy PC
> model, that simply isn't true. All those motherboard devices can easily
> exist (and do!) even if ACPI/PnP don't mention them.
I think that's true except in the case where the Leading Other OS won't
use a device unless it's present in ACPI - that kind of enforcement
tends to concentrate vendors' minds, even if they'd otherwise be busy
filling data tables with garbage.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-05-14 15:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 7:57 [git pull] Input updates for 2.6.34-rc6 Dmitry Torokhov
2010-05-13 14:35 ` Linus Torvalds
2010-05-13 14:47 ` Bastien Nocera
2010-05-13 15:04 ` Linus Torvalds
2010-05-13 15:19 ` Linus Torvalds
2010-05-13 15:50 ` Dmitry Torokhov
2010-05-13 16:16 ` Linus Torvalds
2010-05-13 16:38 ` Randy Dunlap
2010-05-13 20:15 ` Matthew Garrett
2010-05-13 16:01 ` Dmitry Torokhov
2010-05-13 16:54 ` Linus Torvalds
2010-05-13 16:58 ` Linus Torvalds
2010-05-13 17:16 ` Dmitry Torokhov
2010-05-13 17:30 ` Linus Torvalds
2010-05-13 18:10 ` Dmitry Torokhov
2010-05-13 19:55 ` Linus Torvalds
2010-05-14 7:56 ` Eric W. Biederman
2010-05-14 14:54 ` Linus Torvalds
2010-05-14 15:38 ` Matthew Garrett [this message]
2010-05-14 15:42 ` Linus Torvalds
2010-05-14 15:49 ` Matthew Garrett
2010-05-20 4:53 ` Len Brown
2010-05-27 6:22 ` Robert Hancock
2010-05-27 6:43 ` Dmitry Torokhov
2010-05-27 17:06 ` Linus Torvalds
2010-05-27 23:03 ` Robert Hancock
2010-05-28 0:46 ` Linus Torvalds
2010-05-28 1:03 ` Dmitry Torokhov
2010-05-28 4:05 ` Robert Hancock
2010-05-28 5:10 ` Dmitry Torokhov
2010-05-14 14:55 ` Matthew Garrett
2010-05-14 15:16 ` Linus Torvalds
2010-05-14 16:28 ` Dmitry Torokhov
2010-05-14 18:47 ` david
2010-05-14 18:49 ` Matthew Garrett
2010-05-14 18:55 ` david
2010-05-14 18:59 ` Matthew Garrett
2010-05-14 19:05 ` david
2010-05-28 2:38 ` Mike Frysinger
2010-08-04 6:20 ` Dmitry Torokhov
2010-08-04 6:29 ` Dmitry Torokhov
2010-05-14 16:29 ` Dmitry Torokhov
2010-05-14 16:35 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 6:41 Dmitry Torokhov
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=20100514153842.GA6398@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ebiederm@xmission.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).