From: Andi Kleen <andi@firstfloor.org>
To: torvalds@osdl.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Please pull ACPI updates
Date: Thu, 24 Jul 2008 22:36:36 +0200 [thread overview]
Message-ID: <20080724203636.GA22485@basil.nowhere.org> (raw)
Linus,
Please pull ACPI updates from
git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-acpi-2.6.git release-2.6.27
which contains
Andi Kleen (5):
Revert "Fix FADT parsing"
Revert "dock: bay: Don't call acpi_walk_namespace() when ACPI is disabled."
Merge branch 'merge' into release-2.6.27
Revert "ACPI: don't walk tables if ACPI was disabled"
Merge branch 'for-upstream/acpi-test' of git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6 into release-2.6.27
Bjorn Helgaas (1):
ACPI: stop complaints about interrupt link End Tags and blank IRQ descriptors
Henrique de Moraes Holschuh (7):
ACPI: thinkpad-acpi: minor refactor on radio switch init
ACPI: thinkpad-acpi: consolidate wlsw notification function
ACPI: thinkpad-acpi: prepare for bluetooth and wwan rfkill support
ACPI: thinkpad-acpi: WLSW overrides other rfkill switches
ACPI: thinkpad-acpi: add bluetooth and WWAN rfkill support
ACPI: thinkpad-acpi: bump up version to 0.21
ACPI: thinkpad-acpi: don't misdetect in get_thinkpad_model_data() on -ENOMEM
Ingo Molnar (1):
acpi: fix crash in core ACPI code, triggered by CONFIG_ACPI_PCI_SLOT=y
Zhao Yakui (2):
ACPI: Ignore _BQC object when registering backlight device
ACPI : Set FAN device to correct state in boot phase
Documentation/laptops/thinkpad-acpi.txt | 26 ++-
drivers/acpi/namespace/nsnames.c | 8 +
drivers/acpi/pci_link.c | 31 ++-
drivers/acpi/tables/tbfadt.c | 17 +-
drivers/acpi/thermal.c | 43 +++
drivers/acpi/utilities/utalloc.c | 4 +
drivers/acpi/video.c | 14 +-
drivers/misc/Kconfig | 2 +
drivers/misc/thinkpad_acpi.c | 475 ++++++++++++++++++++++---------
9 files changed, 446 insertions(+), 174 deletions(-)
next reply other threads:[~2008-07-24 20:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 20:36 Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 21:45 Please pull ACPI updates Andi Kleen
2008-07-16 22:11 ` Rafael J. Wysocki
2008-07-16 23:33 ` Jesse Barnes
2008-07-16 23:45 ` Linus Torvalds
2008-07-16 23:51 ` Jesse Barnes
2008-07-17 0:32 ` Linus Torvalds
2008-07-17 0:53 ` Linus Torvalds
2008-07-17 2:26 ` Jesse Barnes
2008-07-17 2:56 ` Linus Torvalds
2008-07-17 6:45 ` Andi Kleen
2008-07-17 15:06 ` Linus Torvalds
2008-07-17 6:40 ` Andi Kleen
2008-07-17 15:03 ` Linus Torvalds
2008-07-17 18:49 ` Len Brown
2008-07-17 19:12 ` Harvey Harrison
2008-07-17 19:50 ` Andi Kleen
2008-07-17 19:12 ` Linus Torvalds
2008-07-17 19:16 ` Linus Torvalds
2008-07-17 21:15 ` J. Bruce Fields
2008-07-17 6:47 ` Andi Kleen
2008-07-17 15:18 ` Linus Torvalds
2008-07-17 15:47 ` Linus Torvalds
2008-07-17 16:02 ` Linus Torvalds
2008-07-17 16:23 ` Andi Kleen
2008-07-17 19:11 ` Ray Lee
2008-07-17 19:49 ` Andi Kleen
2008-07-17 20:01 ` Linus Torvalds
2008-07-17 20:14 ` Andi Kleen
2008-07-17 20:16 ` Linus Torvalds
2008-07-17 20:28 ` Linus Torvalds
2008-07-18 13:25 ` Olivier Galibert
2008-07-18 15:57 ` Ray Lee
2008-07-17 20:34 ` Andi Kleen
2008-07-17 20:11 ` Ray Lee
2008-07-17 20:29 ` Andi Kleen
2008-07-18 6:39 ` david
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=20080724203636.GA22485@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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