From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [BKPATCH] ACPI 20030916 for 2.4.23-pre4
Date: 16 Sep 2003 17:50:40 -0700 [thread overview]
Message-ID: <1063759840.13038.23.camel@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.44.0309151824360.2914-100000@logos.cnet>
Hi Marcelo, please do a
bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.4.23
This will update the following files:
arch/i386/kernel/acpi.c | 1
arch/i386/kernel/dmi_scan.c | 9 +---
arch/i386/kernel/mpparse.c | 26 ++++++------
arch/i386/mm/ioremap.c | 2
drivers/acpi/ec.c | 7 ++-
drivers/acpi/events/evregion.c | 6 +-
drivers/acpi/pci_link.c | 61 ++++++++++++++++++++++++-----
include/acpi/acconfig.h | 2
8 files changed, 78 insertions(+), 36 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (03/09/16 1.1063.43.6)
ACPI_CA_VERSION 0x20030916
<len.brown@intel.com> (03/09/12 1.1063.43.5)
fix off-by-one error in ioremap()
fixes kernel crash in acpi mode:
http://bugzilla.kernel.org/show_bug.cgi?id=1085
<len.brown@intel.com> (03/09/08 1.1063.43.4)
remove ASUS A7V BIOS version 1011 from blacklist (Eric Valette)
<len.brown@intel.com> (03/09/08 1.1063.43.3)
support non ACPI compliant SCI over-ride specs (Jun Nakajima)
<len.brown@intel.com> (03/09/08 1.1063.43.2)
Fix ACPI oops on ThinkPad T32/T40 (Shaohua David Li)
<len.brown@intel.com> (03/09/08 1.1063.43.1)
Extended IRQ resource type for nForce (Andrew de Quincey)
Handle BIOS with _CRS that fails (Jun Nakajima)
next prev parent reply other threads:[~2003-09-17 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 21:33 ACPI fixes Marcelo Tosatti
2003-09-15 22:37 ` Andrew de Quincey
2003-09-17 0:50 ` Len Brown [this message]
2003-09-17 1:38 ` [BKPATCH] ACPI 20030916 for 2.4.23-pre4 Len Brown
2003-09-17 7:27 ` [ACPI] " Karol Kozimor
2003-09-17 15:35 ` Jesse Barnes
2003-09-17 15:57 ` Len Brown
2003-09-19 3:49 ` Len Brown
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=1063759840.13038.23.camel@linux.local \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
/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