summaryrefslogtreecommitdiff
path: root/include/acpi/aclocal.h
diff options
context:
space:
mode:
authorLen Brown <len.brown@intel.com>2006-07-08 04:11:07 +0400
committerLen Brown <len.brown@intel.com>2006-07-09 23:19:44 +0400
commitab8aa06a5c0b75974fb1949365cbb20a15cedf14 (patch)
tree8498b3b3222198c45fa322b6fdd3215687dc30e4 /include/acpi/aclocal.h
parent120bda20c6f64b32e8bfbdd7b34feafaa5f5332e (diff)
downloadlinux-ab8aa06a5c0b75974fb1949365cbb20a15cedf14.tar.xz
ACPI: acpi_os_get_thread_id() returns current
Linux mutexes and the debug code that that reference acpi_os_get_thread_id() are happy with 0. But the AML mutexes in exmutex.c expect a unique non-zero number for each thread - as they track this thread_id to permit the mutex re-entrancy defined by the ACPI spec. http://bugzilla.kernel.org/show_bug.cgi?id=6687 Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'include/acpi/aclocal.h')
-rw-r--r--include/acpi/aclocal.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/acpi/aclocal.h b/include/acpi/aclocal.h
index 56b802486161..fbafee6e56d3 100644
--- a/include/acpi/aclocal.h
+++ b/include/acpi/aclocal.h
@@ -127,7 +127,7 @@ typedef u8 acpi_owner_id;
/* This Thread ID means that the mutex is not in use (unlocked) */
-#define ACPI_MUTEX_NOT_ACQUIRED (u32) -1
+#define ACPI_MUTEX_NOT_ACQUIRED (acpi_thread_id) 0
/* Table for the global mutexes */