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 9b462f418b991569e792368e255f177c1ef6d442..70d330142ec4bc894f923f739cff1c160b3e1136 100644 (file)
--- 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 <astarikovskiy@suse.de>
 Date: Mon, 12 Nov 2007 19:06:40 -0500
 Subject: ACPI: sleep: Fix GPE suspend cleanup
 To: linux-stable <stable@kernel.org>
-Cc: "Brown, Len" <len.brown@intel.com>
+Cc: Len Brown <len.brown@intel.com>
 Message-ID: <4738EA90.6090704@redhat.com>
 
 From: Alexey Starikovskiy <astarikovskiy@suse.de>

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 9fe9903e0f423d420dd85450aff673100f2c0312..4e28cb3806dfbd3644d1cd7f85c8271aab3ff1e4 100644 (file)
--- 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 <astarikovskiy@suse.de>
 Date: Mon, 12 Nov 2007 19:09:01 -0500
 Subject: ACPI: suspend: Wrong order of GPE restore.
 To: linux-stable <stable@kernel.org>
-Cc: "Brown, Len" <len.brown@intel.com>
+Cc: Len Brown <len.brown@intel.com>
 Message-ID: <4738EB1D.6030709@redhat.com>
 
 From: Alexey Starikovskiy <astarikovskiy@suse.de>

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 912e24be8a2a47bddddaa578ed71e3c95bab491f..a47e800ec107fd8c4b184025993b8cd100687189 100644 (file)
--- 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 <ghaskins@novell.com>
 Date: Thu, 11 Oct 2007 22:11:11 +0200
 Subject: [PATCH] lockdep: fix mismatched lockdep_depth/curr_chain_hash
+
+From: Gregory Haskins <ghaskins@novell.com>
+
+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