diff for duplicates of <87k5uimzkh.fsf@wanadoo.fr>

diff --git a/a/1.txt b/N1/1.txt
index efd43ca..1f44e75 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -28,7 +28,7 @@ it for each maintainer ?
 >>  
 >> -                    data = kmalloc(xc.len, GFP_KERNEL);
 >> +                    data = kmalloc(xc.len, GFP_ATOMIC);
->>                      if(data = 0x0){
+>>                      if(data == 0x0){
 >>                              printk(KERN_WARNING "%s: Failed to allocate memory for copy\n", dev->name);
 >>                              ret = -ENOMEM;
 >
@@ -85,9 +85,3 @@ Ok. Do you have a preference on the format ?  a <file>:<line> format  ?
 Is there a place that gathered all those implicit programming rules 
 (that copy_from_user must not be called inside a spinlock, etc) so that
 I can translate them in a script for our tool.
-
-
-_______________________________________________
-Kernel-janitors mailing list
-Kernel-janitors@lists.linux-foundation.org
-https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
diff --git a/a/content_digest b/N1/content_digest
index 1b0b9d5..390e93a 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,8 @@
  "ref\087odjvu1on.fsf@wanadoo.fr\0"
  "ref\020070604210018.0eaa20a0.akpm@linux-foundation.org\0"
  "From\0Yoann Padioleau <padator@wanadoo.fr>\0"
- "Subject\0Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked\0"
- "Date\0Tue, 05 Jun 2007 11:05:18 +0000\0"
+ "Subject\0Re: [KJ] Re: [PATCH] bugfix GFP_KERNEL -> GFP_ATOMIC in spin_locked region\0"
+ "Date\0Tue, 05 Jun 2007 13:05:18 +0200\0"
  "To\0Andrew Morton <akpm@linux-foundation.org>\0"
  "Cc\0linux-kernel@vger.kernel.org"
  " kernel-janitors@lists.osdl.org\0"
@@ -38,7 +38,7 @@
  ">>  \n"
  ">> -                    data = kmalloc(xc.len, GFP_KERNEL);\n"
  ">> +                    data = kmalloc(xc.len, GFP_ATOMIC);\n"
- ">>                      if(data = 0x0){\n"
+ ">>                      if(data == 0x0){\n"
  ">>                              printk(KERN_WARNING \"%s: Failed to allocate memory for copy\\n\", dev->name);\n"
  ">>                              ret = -ENOMEM;\n"
  ">\n"
@@ -94,12 +94,6 @@
  "\n"
  "Is there a place that gathered all those implicit programming rules \n"
  "(that copy_from_user must not be called inside a spinlock, etc) so that\n"
- "I can translate them in a script for our tool.\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "Kernel-janitors mailing list\n"
- "Kernel-janitors@lists.linux-foundation.org\n"
- https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
+ I can translate them in a script for our tool.
 
-82dbea3175adbafe50c6639a4d41f62622e5e0509b3f8a84c227bd2a692f71f5
+3fd1e6411dc38bf0e514ea7ee77b565d47f3492892ae93d4d70307b2d6067b5e
