From: Jesse Barnes <jbarnes-UzQTBcouhwxWk0Htik3J/w@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [BKPATCH] ACPI for 2.6
Date: Sat, 14 Aug 2004 13:56:51 -0700 [thread overview]
Message-ID: <200408141356.51746.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1092466509.5028.248.camel@dhcppc4>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On Friday, August 13, 2004 11:55 pm, Len Brown wrote:
> Hi Linus, please do a
>
> bk pull bk://linux-acpi.bkbits.net/linux-acpi-release-2.6.8
>
> Key fixes for suspend/resume, a couple of common
> boot failures, and misc. random fixes.
You'll need this fix for ia64 though. Linus, please apply.
Define acpi_noirq on ia64 since it's used now in pci_link.c. All ia64
machines use ACPI, so we can just define it to 0 like we do for acpi_disabled
and acpi_pci_disabled.
Signed-off-by: Jesse Barnes <jbarnes-sJ/iWh9BUns@public.gmane.org>
Thanks,
Jesse
[-- Attachment #2: ia64-acpi-build-fix.patch --]
[-- Type: text/x-diff, Size: 702 bytes --]
diff -Napur -X /home/jbarnes/dontdiff linux-2.6.8-rc4.orig/include/asm-ia64/acpi.h linux-2.6.8-rc4/include/asm-ia64/acpi.h
--- linux-2.6.8-rc4.orig/include/asm-ia64/acpi.h 2004-08-10 09:01:34.000000000 -0700
+++ linux-2.6.8-rc4/include/asm-ia64/acpi.h 2004-08-10 09:26:39.000000000 -0700
@@ -89,6 +89,7 @@ ia64_acpi_release_global_lock (unsigned
((Acq) = ia64_acpi_release_global_lock((unsigned int *) GLptr))
#define acpi_disabled 0 /* ACPI always enabled on IA64 */
+#define acpi_noirq 0 /* ACPI always enabled on IA64 */
#define acpi_pci_disabled 0 /* ACPI PCI always enabled on IA64 */
#define acpi_strict 1 /* no ACPI spec workarounds on IA64 */
static inline void disable_acpi(void) { }
WARNING: multiple messages have this Message-ID (diff)
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Len Brown <len.brown@intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [BKPATCH] ACPI for 2.6
Date: Sat, 14 Aug 2004 13:56:51 -0700 [thread overview]
Message-ID: <200408141356.51746.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1092466509.5028.248.camel@dhcppc4>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Friday, August 13, 2004 11:55 pm, Len Brown wrote:
> Hi Linus, please do a
>
> bk pull bk://linux-acpi.bkbits.net/linux-acpi-release-2.6.8
>
> Key fixes for suspend/resume, a couple of common
> boot failures, and misc. random fixes.
You'll need this fix for ia64 though. Linus, please apply.
Define acpi_noirq on ia64 since it's used now in pci_link.c. All ia64
machines use ACPI, so we can just define it to 0 like we do for acpi_disabled
and acpi_pci_disabled.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Thanks,
Jesse
[-- Attachment #2: ia64-acpi-build-fix.patch --]
[-- Type: text/x-diff, Size: 702 bytes --]
diff -Napur -X /home/jbarnes/dontdiff linux-2.6.8-rc4.orig/include/asm-ia64/acpi.h linux-2.6.8-rc4/include/asm-ia64/acpi.h
--- linux-2.6.8-rc4.orig/include/asm-ia64/acpi.h 2004-08-10 09:01:34.000000000 -0700
+++ linux-2.6.8-rc4/include/asm-ia64/acpi.h 2004-08-10 09:26:39.000000000 -0700
@@ -89,6 +89,7 @@ ia64_acpi_release_global_lock (unsigned
((Acq) = ia64_acpi_release_global_lock((unsigned int *) GLptr))
#define acpi_disabled 0 /* ACPI always enabled on IA64 */
+#define acpi_noirq 0 /* ACPI always enabled on IA64 */
#define acpi_pci_disabled 0 /* ACPI PCI always enabled on IA64 */
#define acpi_strict 1 /* no ACPI spec workarounds on IA64 */
static inline void disable_acpi(void) { }
next prev parent reply other threads:[~2004-08-14 20:56 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 6:55 [BKPATCH] ACPI for 2.6 Len Brown
2004-08-14 20:56 ` Jesse Barnes [this message]
2004-08-14 20:56 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 7:47 Len Brown
2004-11-09 7:47 ` 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-12-01 23:13 ` Len Brown
2004-10-09 5:54 Len Brown
2004-08-14 23:08 Len Brown
[not found] <566B962EB122634D86E6EE29E83DD808182C3286@hdsmsx403.hd.intel.com>
2004-08-14 18:43 ` Len Brown
2004-08-15 16:58 ` Marcus Hartig
2004-08-14 16:40 Marcus Hartig
2004-06-21 19:41 Len Brown
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
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-20 19:12 ` Len Brown
2004-05-11 16:48 Len Brown
2004-05-11 16:48 ` Len Brown
2004-05-03 16:52 Len Brown
2004-04-01 10:40 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
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-27 11:11 ` Marcel Holtmann
2004-03-23 10:02 Len Brown
2004-03-23 10:02 ` Len Brown
2004-03-14 6:08 Len Brown
2004-03-14 6:08 ` Len Brown
2004-03-06 6:37 Len Brown
2004-03-06 6:37 ` Len Brown
2004-02-25 9:18 Len Brown
2004-02-25 9:18 ` Len Brown
2004-02-14 4:46 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:09 ` Olaf Hering
2004-02-09 9:11 ` Olaf Hering
2004-02-09 9:11 ` Olaf Hering
2004-01-27 6:03 Len Brown
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=200408141356.51746.jbarnes@engr.sgi.com \
--to=jbarnes-uzqtbcouhwxwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-3NddpPZAyC0@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.