All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <87y3kxrrc2.fsf@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index 22c5dba..29cb1a4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,18 +3,16 @@ Christophe LEROY <christophe.leroy@c-s.fr> writes:
 >>
 >>> How should I split in separate patches ? Something like ?
 >>> 1/ Slice support for PPC32 > 2/ Activate slice for 8xx
->>=20
->> Yes something like that. Will you=C2=A0 be able to avoid that
->>  =C2=A0if (SLICE_NUM_HIGH) from the code? That makes the code ugly. Righ=
-t now=20
+>> 
+>> Yes something like that. Will you  be able to avoid that
+>>   if (SLICE_NUM_HIGH) from the code? That makes the code ugly. Right now 
 >> i don't have definite suggestion on what we could do though.
->>=20
+>> 
 >
 > Could use #ifdefs instead, but in my mind it would be even more ugly.
 >
-> I would have liked just doing nothing, but the issue is that at the=20
-> moment bitmap_xxx() functions are not prepared to handle bitmaps of size=
-=20
+> I would have liked just doing nothing, but the issue is that at the 
+> moment bitmap_xxx() functions are not prepared to handle bitmaps of size 
 > zero. Should we try to change that ? Any chance to succeed ?
 >
 
diff --git a/a/content_digest b/N1/content_digest
index 8bfa452..c087d02 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -21,18 +21,16 @@
  ">>\n"
  ">>> How should I split in separate patches ? Something like ?\n"
  ">>> 1/ Slice support for PPC32 > 2/ Activate slice for 8xx\n"
- ">>=20\n"
- ">> Yes something like that. Will you=C2=A0 be able to avoid that\n"
- ">>  =C2=A0if (SLICE_NUM_HIGH) from the code? That makes the code ugly. Righ=\n"
- "t now=20\n"
+ ">> \n"
+ ">> Yes something like that. Will you\302\240 be able to avoid that\n"
+ ">>  \302\240if (SLICE_NUM_HIGH) from the code? That makes the code ugly. Right now \n"
  ">> i don't have definite suggestion on what we could do though.\n"
- ">>=20\n"
+ ">> \n"
  ">\n"
  "> Could use #ifdefs instead, but in my mind it would be even more ugly.\n"
  ">\n"
- "> I would have liked just doing nothing, but the issue is that at the=20\n"
- "> moment bitmap_xxx() functions are not prepared to handle bitmaps of size=\n"
- "=20\n"
+ "> I would have liked just doing nothing, but the issue is that at the \n"
+ "> moment bitmap_xxx() functions are not prepared to handle bitmaps of size \n"
  "> zero. Should we try to change that ? Any chance to succeed ?\n"
  ">\n"
  "\n"
@@ -44,4 +42,4 @@
  "\n"
  -aneesh
 
-a25622b341a516b5680d8e7d7ab278c22fc894d6b431abaa5383cf6e90e08aa0
+cbb6507b174beca4b0dcf3f82d90fc611f14be04a8c0bae82d2ddcdefefe9084

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.