All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1504608384.22554.17.camel@nxp.com>

diff --git a/a/content_digest b/N1/content_digest
index 7aee30b..660e090 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,7 +4,7 @@
  "ref\0CAJcbSZEd10fMp6OSgSYv_Wmt=wX5fw_Gu-_N=fM_QmP==wUMew@mail.gmail.com\0"
  "ref\0CAGXu5jKuk9589qap=74kPtefm=xKY0ORDH37W_3iZPd_7yc8VQ@mail.gmail.com\0"
  "From\0Leonard Crestez <leonard.crestez@nxp.com>\0"
- "Subject\0[kernel-hardening] Re: [PATCH v3 3/4] arm/syscalls: Optimize address limit check\0"
+ "Subject\0Re: [PATCH v3 3/4] arm/syscalls: Optimize address limit check\0"
  "Date\0Tue, 5 Sep 2017 13:46:24 +0300\0"
  "To\0Kees Cook <keescook@chromium.org>"
   Thomas Gleixner <tglx@linutronix.de>
@@ -96,4 +96,4 @@
  "Regards,\n"
  Leonard
 
-c78b09f5b851fe6fccfebdb72f95df294ae9a8b0da216c72118892e2d7eff920
+f0ee50ebdda44ae9710a6edffd9825515c4bf6766233a1bd400215ba1aff5d23

diff --git a/a/1.txt b/N2/1.txt
index 84c58db..2a7d2c2 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -22,7 +22,7 @@ On Tue, 2017-08-29 at 12:54 -0700, Kees Cook wrote:
 
 > > > Any feedback?
 
-> > CCing LW@karo-electronics.de who experienced the same issue this patch
+> > CCing LW at karo-electronics.de who experienced the same issue this patch
 > > proposal fix.
 > > 
 > > Russell: Any feedback?
@@ -56,7 +56,7 @@ patch should be reverted first, separately? In this particular case the
 series fixing the bug actually includes the revert.
 
 Anyway, I check that this v3 works on my board which was reproducing
-the issue while booting from nfs (imx6sl-evk). The most likely reason
+the issue while booting from nfs (imx6sl-evk).?The most likely reason
 it's easy to reproduce here is a network driver issue where headers are
 not correctly aligned to 4. This causes lots of alignment faults.
 
diff --git a/a/content_digest b/N2/content_digest
index 7aee30b..f04c35b 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,29 +3,10 @@
  "ref\0CAJcbSZG1b7ObJAv6Kmp-fR3vZRg7AdbcgqDceGB95r-72Yv0yg@mail.gmail.com\0"
  "ref\0CAJcbSZEd10fMp6OSgSYv_Wmt=wX5fw_Gu-_N=fM_QmP==wUMew@mail.gmail.com\0"
  "ref\0CAGXu5jKuk9589qap=74kPtefm=xKY0ORDH37W_3iZPd_7yc8VQ@mail.gmail.com\0"
- "From\0Leonard Crestez <leonard.crestez@nxp.com>\0"
- "Subject\0[kernel-hardening] Re: [PATCH v3 3/4] arm/syscalls: Optimize address limit check\0"
+ "From\0leonard.crestez@nxp.com (Leonard Crestez)\0"
+ "Subject\0[PATCH v3 3/4] arm/syscalls: Optimize address limit check\0"
  "Date\0Tue, 5 Sep 2017 13:46:24 +0300\0"
- "To\0Kees Cook <keescook@chromium.org>"
-  Thomas Gleixner <tglx@linutronix.de>
-  Thomas Garnier <thgarnie@google.com>
-  Russell King <linux@armlinux.org.uk>
- " Ingo Molnar <mingo@redhat.com>\0"
- "Cc\0Will Drewry <wad@chromium.org>"
-  Arnd Bergmann <arnd@arndb.de>
-  Kernel Hardening <kernel-hardening@lists.openwall.com>
-  Catalin Marinas <catalin.marinas@arm.com>
-  Will Deacon <will.deacon@arm.com>
-  LKML <linux-kernel@vger.kernel.org>
-  Andy Lutomirski <luto@amacapital.net>
-  David Howells <dhowells@redhat.com>
-  Dave Hansen <dave.hansen@intel.com>
-  Al Viro <viro@zeniv.linux.org.uk>
-  Linux API <linux-api@vger.kernel.org>
-  Yonghong Song <yhs@fb.com>
-  Dave Martin <Dave.Martin@arm.com>
-  Linux ARM <linux-arm-kernel@lists.infradead.org>
- " Lothar Wa\303\237mann <LW@karo-electronics.de>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, 2017-08-29 at 12:54 -0700, Kees Cook wrote:\n"
@@ -52,7 +33,7 @@
  "\n"
  "> > > Any feedback?\n"
  "\n"
- "> > CCing LW@karo-electronics.de who experienced the same issue this patch\n"
+ "> > CCing LW at karo-electronics.de who experienced the same issue this patch\n"
  "> > proposal fix.\n"
  "> > \n"
  "> > Russell: Any feedback?\n"
@@ -86,7 +67,7 @@
  "series fixing the bug actually includes the revert.\n"
  "\n"
  "Anyway, I check that this v3 works on my board which was reproducing\n"
- "the issue while booting from nfs (imx6sl-evk).\302\240The most likely reason\n"
+ "the issue while booting from nfs (imx6sl-evk).?The most likely reason\n"
  "it's easy to reproduce here is a network driver issue where headers are\n"
  "not correctly aligned to 4. This causes lots of alignment faults.\n"
  "\n"
@@ -96,4 +77,4 @@
  "Regards,\n"
  Leonard
 
-c78b09f5b851fe6fccfebdb72f95df294ae9a8b0da216c72118892e2d7eff920
+f0e7b465bee0e6a8295360e08d6789f8b587ee108ee5ba6cfaf7164608e5f138

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.