diff for duplicates of <201905221316.865581CF@keescook> diff --git a/a/1.txt b/N1/1.txt index 4cc0a86..39845e5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Wed, May 22, 2019 at 05:35:27PM +0100, Catalin Marinas wrote: +On Wed, May 22, 2019@05:35:27PM +0100, Catalin Marinas wrote: > The two hard requirements I have for supporting any new hardware feature > in Linux are (1) a single kernel image binary continues to run on old > hardware while making use of the new feature if available and (2) old diff --git a/a/content_digest b/N1/content_digest index 2f9c485..b746497 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,12 +6,12 @@ "ref\020190522101110.m2stmpaj7seezveq@mbp\0" "ref\0CAJgzZoosKBwqXRyA6fb8QQSZXFqfHqe9qO9je5TogHhzuoGXJQ@mail.gmail.com\0" "ref\020190522163527.rnnc6t4tll7tk5zw@mbp\0" - "From\0keescook at chromium.org (Kees Cook)\0" + "From\0keescook@chromium.org (Kees Cook)\0" "Subject\0[PATCH v15 00/17] arm64: untag user pointers passed to the kernel\0" "Date\0Wed, 22 May 2019 13:47:36 -0700\0" "\00:1\0" "b\0" - "On Wed, May 22, 2019 at 05:35:27PM +0100, Catalin Marinas wrote:\n" + "On Wed, May 22, 2019@05:35:27PM +0100, Catalin Marinas wrote:\n" "> The two hard requirements I have for supporting any new hardware feature\n" "> in Linux are (1) a single kernel image binary continues to run on old\n" "> hardware while making use of the new feature if available and (2) old\n" @@ -75,4 +75,4 @@ "-- \n" Kees Cook -dd172713dc003f354b4182b39ff8625f28343651179687e3229eeef6723be9b5 +bac0f47f42af80322ae9ba026ccaca66f5e89649408d70dfecabfb5554c8924c
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox