From: Greg Kroah-Hartman Date: Thu, 15 Nov 2007 06:24:46 +0000 (-0800) Subject: some patch cleanups on headers X-Git-Tag: v2.6.23.2~6 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2a9e2c78effb8fd77776857fd4aac66fc8ecf42c;p=thirdparty%2Fkernel%2Fstable-queue.git some patch cleanups on headers --- diff --git a/queue-2.6.23/acpi-sleep-fix-gpe-suspend-cleanup.patch b/queue-2.6.23/acpi-sleep-fix-gpe-suspend-cleanup.patch index 9b462f418b9..70d330142ec 100644 --- a/queue-2.6.23/acpi-sleep-fix-gpe-suspend-cleanup.patch +++ b/queue-2.6.23/acpi-sleep-fix-gpe-suspend-cleanup.patch @@ -3,7 +3,7 @@ From: Alexey Starikovskiy Date: Mon, 12 Nov 2007 19:06:40 -0500 Subject: ACPI: sleep: Fix GPE suspend cleanup To: linux-stable -Cc: "Brown, Len" +Cc: Len Brown Message-ID: <4738EA90.6090704@redhat.com> From: Alexey Starikovskiy diff --git a/queue-2.6.23/acpi-suspend-wrong-order-of-gpe-restore.patch b/queue-2.6.23/acpi-suspend-wrong-order-of-gpe-restore.patch index 9fe9903e0f4..4e28cb3806d 100644 --- a/queue-2.6.23/acpi-suspend-wrong-order-of-gpe-restore.patch +++ b/queue-2.6.23/acpi-suspend-wrong-order-of-gpe-restore.patch @@ -3,7 +3,7 @@ From: Alexey Starikovskiy Date: Mon, 12 Nov 2007 19:09:01 -0500 Subject: ACPI: suspend: Wrong order of GPE restore. To: linux-stable -Cc: "Brown, Len" +Cc: Len Brown Message-ID: <4738EB1D.6030709@redhat.com> From: Alexey Starikovskiy diff --git a/queue-2.6.23/lockdep-fix-mismatched-lockdep_depth-curr_chain_hash.patch b/queue-2.6.23/lockdep-fix-mismatched-lockdep_depth-curr_chain_hash.patch index 912e24be8a2..a47e800ec10 100644 --- a/queue-2.6.23/lockdep-fix-mismatched-lockdep_depth-curr_chain_hash.patch +++ b/queue-2.6.23/lockdep-fix-mismatched-lockdep_depth-curr_chain_hash.patch @@ -2,6 +2,12 @@ From 3aa416b07f0adf01c090baab26fb70c35ec17623 Mon Sep 17 00:00:00 2001 From: Gregory Haskins Date: Thu, 11 Oct 2007 22:11:11 +0200 Subject: [PATCH] lockdep: fix mismatched lockdep_depth/curr_chain_hash + +From: Gregory Haskins + +patch 3aa416b07f0adf01c090baab26fb70c35ec17623 in mainline. + + It is possible for the current->curr_chain_key to become inconsistent with the current index if the chain fails to validate. The end result is that future lock_acquire() operations may inadvertently fail to find a hit in the cache