From: Len Brown <len.brown@intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: [BKPATCH] ACPI for 2.6
Date: 13 Feb 2004 23:46:51 -0500 [thread overview]
Message-ID: <1076734010.25353.65.camel@dhcppc4> (raw)
Hi Linus, please do a
bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.6.3
thanks,
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.3/acpi-20040116-2.6.3.diff.gz
This will update the following files:
arch/i386/Kconfig | 6 +++---
arch/i386/kernel/acpi/boot.c | 4 ++++
arch/i386/kernel/mpparse.c | 11 ++++++-----
arch/x86_64/kernel/acpi/boot.c | 5 +++++
arch/x86_64/kernel/mpparse.c | 13 +++++++------
drivers/acpi/Kconfig | 2 +-
drivers/acpi/numa.c | 2 +-
drivers/acpi/processor.c | 6 +++---
8 files changed, 30 insertions(+), 19 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (04/02/13 1.1603.11.7)
[ACPI] interrupt over-ride fix from i386 (Maciej W. Rozycki)
<akpm@osdl.org> (04/02/11 1.1500.36.5)
[PATCH] acpi cpu_has_cpufreq() fix
Call that function rather than evaluating its runtime address...
<len.brown@intel.com> (04/02/11 1.1500.36.4)
[ACPI] clarify error message in processor.c
<len.brown@intel.com> (04/02/10 1.1603.11.4)
[ACPI] don't register disabled processors -- it just confuses people
<len.brown@intel.com> (04/02/10 1.1603.11.3)
[ACPI] delete mention of stale config option ACPI_HT_ONLY
<len.brown@intel.com> (04/02/10 1.1500.36.2)
[ACPI] NUMA build fix -- NR_MEMBLKS is now NR_NODE_MEMBLKS
<mbligh@aracnet.com> (04/02/10 1.1603.11.1)
[PATCH] NUMA build fix
drivers/acpi/numa.c is IA64 only for now -- enforce it.
(and arch/i386/kernel/srat.c is i386 only for now)
<len.brown@intel.com> (04/02/07 1.1493.1.17)
[ACPI] nforce2 timer lockup from Maciej W. Rozycki
next reply other threads:[~2004-02-14 4:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 4:46 Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 7:47 [BKPATCH] ACPI for 2.6 Len Brown
2004-11-12 17:42 ` Pavel Machek
[not found] ` <20041112174248.GA4267-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-01 23:13 ` Len Brown
2004-10-09 5:54 Len Brown
2004-08-14 6:55 Len Brown
2004-08-14 20:56 ` Jesse Barnes
2004-06-21 19:41 Len Brown
[not found] <E1BbPIM-00044a-0A@sc8-sf-list2.sourceforge.net>
[not found] ` <E1BbPIM-00044a-0A-ek0oC1U1TqqnvZpeIfgr/KQD96bmaF075NbjCUgZEJk@public.gmane.org>
2004-06-19 21:22 ` Carsten Rietzschel
2004-06-18 6:42 Len Brown
[not found] ` <1087540933.4487.212.camel-D2Zvc0uNKG8@public.gmane.org>
2004-06-23 13:47 ` Stefan Seyfried
2004-05-20 19:12 Len Brown
2004-05-11 16:48 Len Brown
2004-05-03 16:52 Len Brown
2004-04-01 10:40 Len Brown
2004-03-30 1:26 Manpreet Singh
2004-03-30 0:28 Manpreet Singh
2004-03-29 17:32 Moore, Robert
2004-03-27 9:18 Manpreet Singh
2004-03-27 0:59 Len Brown
[not found] ` <1080349151.16211.33.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-27 11:11 ` Marcel Holtmann
2004-03-23 10:02 Len Brown
2004-03-14 6:08 Len Brown
2004-03-06 6:37 Len Brown
2004-02-25 9:18 Len Brown
2004-02-07 9:10 Len Brown
[not found] ` <1076145027.8682.34.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-09 9:09 ` Olaf Hering
2004-02-09 9:11 ` Olaf Hering
2004-01-27 6:03 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=1076734010.25353.65.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--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