All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170421100233.GA20029@samekh>

diff --git a/a/1.txt b/N1/1.txt
index c708656..3deccf2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -289,7 +289,7 @@ If not, I believe that the fact that we are removing one aligned GB per
 shot should guarantee that we never have to split a PUD.
 
 However, we should definitely handle all the cases. Since splitting a
-P[UM]D might be a nightmare (if possible@all), two more or less clean
+P[UM]D might be a nightmare (if possible at all), two more or less clean
 solutions I can think of are:
 1. Only allow to hot-remove memory that was previously hot-added or,
 2. Detect when we are trying to only partially remove a section mapped
diff --git a/a/content_digest b/N1/content_digest
index 3327504..ca779ac 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,10 +3,19 @@
  "ref\020170411171210.GD32267@leverpostej\0"
  "ref\020170414140158.GA17950@samekh\0"
  "ref\020170418182125.GL17866@leverpostej\0"
- "From\0ar@linux.vnet.ibm.com (Andrea Reale)\0"
- "Subject\0[PATCH 4/5] Hot-remove implementation for arm64\0"
+ "From\0Andrea Reale <ar@linux.vnet.ibm.com>\0"
+ "Subject\0Re: [PATCH 4/5] Hot-remove implementation for arm64\0"
  "Date\0Fri, 21 Apr 2017 11:02:34 +0100\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Mark Rutland <mark.rutland@arm.com>\0"
+ "Cc\0linux-arm-kernel@lists.infradead.org"
+  f.fainelli@gmail.com
+  m.bielski@virtualopensystems.com
+  scott.branden@broadcom.com
+  will.deacon@arm.com
+  linux-kernel@vger.kernel.org
+  qiuxishi@huawei.com
+  Ard Biesheuvel <ard.biesheuvel@linaro.org>
+ " Laura Abbott <labbott@redhat.com>\0"
  "\00:1\0"
  "b\0"
  "Hi all,\n"
@@ -300,7 +309,7 @@
  "shot should guarantee that we never have to split a PUD.\n"
  "\n"
  "However, we should definitely handle all the cases. Since splitting a\n"
- "P[UM]D might be a nightmare (if possible@all), two more or less clean\n"
+ "P[UM]D might be a nightmare (if possible at all), two more or less clean\n"
  "solutions I can think of are:\n"
  "1. Only allow to hot-remove memory that was previously hot-added or,\n"
  "2. Detect when we are trying to only partially remove a section mapped\n"
@@ -321,4 +330,4 @@
  "Thanks again and best regards,\n"
  Andrea
 
-4053df91ee503bb3a84e3e30bb3be977dd5b96e12ffabfefb5d96147d6ac7c8c
+9bdf83e5197836822e237000fc9d1d9cc839471948d76681aae3cbbab41d4ef4

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.