From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"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: Thu, 20 May 2010 00:53:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1005200025360.2921@localhost.localdomain> (raw)
In-Reply-To: <20100514154905.GA6681@srcf.ucam.org>
> Also, even with Windows, I do wonder if they have things like cut-off
> dates for trusting ACPI. We certainly do.
Upstream Linux's main ACPI cutoff, CONFIG_ACPI_BLACKLIST_YEAR
has been disabled by default since Linux-2.6.9.
So if a platform claims to support ACPI,
upstream Linux has run in ACPI mode on it for many years.
The idea was that we'd harvest and debug ACPI failures
using the upstream kernels, while the distros could play it safe
and set the cutoff to 1999 or even later.
But a funny thing happened a few years ago.
The distros stopped setting this cutoff, and nobody complained.
Of course, it could simply be that few people are using machines
that old anymore...
In any case, I expect that versions of Windows around 1999 or 2000
had to check, but that like Linux, they don't really need to anymore.
cheers,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-05-20 4:54 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
2010-05-14 15:42 ` Linus Torvalds
2010-05-14 15:49 ` Matthew Garrett
2010-05-20 4:53 ` Len Brown [this message]
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=alpine.LFD.2.00.1005200025360.2921@localhost.localdomain \
--to=lenb@kernel.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=mjg59@srcf.ucam.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