Patch formatting updates for release.

diff --git a/review/module-per-cpu-alignment-fix.patch b/review/module-per-cpu-alignment-fix.patch
index a87f973a2a3854be0d61ffa64aadf1e6fc4339aa..381ee85cf4ccfb55ff1ddb819020ca1932ad5107 100644 (file)
--- a/review/module-per-cpu-alignment-fix.patch
+++ b/review/module-per-cpu-alignment-fix.patch
@@ -7,7 +7,7 @@ Subject: [PATCH] Module per-cpu alignment cannot always be met
 
 From: Rusty Russell <rusty@rustcorp.com.au>
 
-[PATCH] Module per-cpu alignment cannot always be met
+Fwd from Daniel Drake <dsd@gentoo.org>.
 
 The module code assumes noone will ever ask for a per-cpu area more than
 SMP_CACHE_BYTES aligned.  However, as these cases show, gcc asks sometimes

diff --git a/review/sys_set_mempolicy-mode-check.patch b/review/sys_set_mempolicy-mode-check.patch
index 7d04d07d5e9dfdf7a26a2bf3156ce2ffdd2c2d09..949b659a6cfff01d32469199da8a503df2eabd56 100644 (file)
--- a/review/sys_set_mempolicy-mode-check.patch
+++ b/review/sys_set_mempolicy-mode-check.patch
@@ -6,8 +6,6 @@ Subject: [PATCH] sys_set_mempolicy() doesnt check if mode < 0
 
 From: Eric Dumazet <dada1@cosmosbay.com>
 
-[PATCH] sys_set_mempolicy() doesnt check if mode < 0
-
 A kernel BUG() is triggered by a call to set_mempolicy() with a negative
 first argument.  This is because the mode is declared as an int, and the
 validity check doesnt check < 0 values.  Alternatively, mode could be

diff --git a/review/x86_64-srat-dual-core-amd.patch b/review/x86_64-srat-dual-core-amd.patch
index bb9435736f30857b4b00b187ae3a526b95333daa..0ff68cc0b8a6889ff062eb135f81f87c6ebef408 100644 (file)
--- a/review/x86_64-srat-dual-core-amd.patch
+++ b/review/x86_64-srat-dual-core-amd.patch
@@ -13,6 +13,7 @@ Just drop the bogus check.
 Signed-off-by: Andi Kleen <ak@suse.de>
 Signed-off-by: Chris Wright <chrisw@osdl.org>
 Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
+---
 
 Index: linux-2.6.12/arch/x86_64/kernel/setup.c
 ===================================================================