All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4EE6BC9B.4000602@freescale.com>

diff --git a/a/1.txt b/N1/1.txt
index f2309be..ab0f021 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,12 +1,17 @@
-于 2011年12月13日 05:30, Scott Wood 写道:
+=E4=BA=8E 2011=E5=B9=B412=E6=9C=8813=E6=97=A5 05:30, Scott Wood =E5=86=99=
+=E9=81=93:
 > On 12/12/2011 03:19 PM, Artem Bityutskiy wrote:
 >> On Mon, 2011-12-12 at 15:15 -0600, Scott Wood wrote:
 >>> NAND chips come from the factory with bad blocks marked at a certain
 >>> offset into each page.  This offset is normally in the OOB area, but
->>> since we change the layout from "4k data, 128 byte oob" to "2k data, 64
->>> byte oob, 2k data, 64 byte oob" the marker is no longer in the oob.  On
->>> first use we need to migrate the markers so that they are still in the oob.
->> Ah, I see, thanks. Are you planning to implement in-kernel migration or
+>>> since we change the layout from "4k data, 128 byte oob" to "2k data, =
+64
+>>> byte oob, 2k data, 64 byte oob" the marker is no longer in the oob.  =
+On
+>>> first use we need to migrate the markers so that they are still in th=
+e oob.
+>> Ah, I see, thanks. Are you planning to implement in-kernel migration o=
+r
 >> use a user-space tool?
 > That's the kind of answer I was hoping to get from Shuo. :-)
 OK, I try to do this. Wait for a couple of days.
@@ -18,7 +23,8 @@ OK, I try to do this. Wait for a couple of days.
 > been migrated (or at least yell loudly in the log).
 >
 > Speaking of raw accesses, these are currently broken in the eLBC
-> driver... we need some way for the generic layer to tell us what kind of
+> driver... we need some way for the generic layer to tell us what kind o=
+f
 > access it is before the transaction starts, not once it wants to read
 > out the buffer (unless we add more hacks to delay the start of a read
 > transaction until first buffer access...).  We'd be better off with a
diff --git a/a/content_digest b/N1/content_digest
index 2f009a4..debc192 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -16,19 +16,23 @@
   shuo.liu@freescale.com
   linux-mtd@lists.infradead.org
   akpm@linux-foundation.org
-  leoli@freescale.com
  " dwmw2@infradead.org\0"
  "\00:1\0"
  "b\0"
- "\344\272\216 2011\345\271\26412\346\234\21013\346\227\245 05:30, Scott Wood \345\206\231\351\201\223:\n"
+ "=E4=BA=8E 2011=E5=B9=B412=E6=9C=8813=E6=97=A5 05:30, Scott Wood =E5=86=99=\n"
+ "=E9=81=93:\n"
  "> On 12/12/2011 03:19 PM, Artem Bityutskiy wrote:\n"
  ">> On Mon, 2011-12-12 at 15:15 -0600, Scott Wood wrote:\n"
  ">>> NAND chips come from the factory with bad blocks marked at a certain\n"
  ">>> offset into each page.  This offset is normally in the OOB area, but\n"
- ">>> since we change the layout from \"4k data, 128 byte oob\" to \"2k data, 64\n"
- ">>> byte oob, 2k data, 64 byte oob\" the marker is no longer in the oob.  On\n"
- ">>> first use we need to migrate the markers so that they are still in the oob.\n"
- ">> Ah, I see, thanks. Are you planning to implement in-kernel migration or\n"
+ ">>> since we change the layout from \"4k data, 128 byte oob\" to \"2k data, =\n"
+ "64\n"
+ ">>> byte oob, 2k data, 64 byte oob\" the marker is no longer in the oob.  =\n"
+ "On\n"
+ ">>> first use we need to migrate the markers so that they are still in th=\n"
+ "e oob.\n"
+ ">> Ah, I see, thanks. Are you planning to implement in-kernel migration o=\n"
+ "r\n"
  ">> use a user-space tool?\n"
  "> That's the kind of answer I was hoping to get from Shuo. :-)\n"
  "OK, I try to do this. Wait for a couple of days.\n"
@@ -40,7 +44,8 @@
  "> been migrated (or at least yell loudly in the log).\n"
  ">\n"
  "> Speaking of raw accesses, these are currently broken in the eLBC\n"
- "> driver... we need some way for the generic layer to tell us what kind of\n"
+ "> driver... we need some way for the generic layer to tell us what kind o=\n"
+ "f\n"
  "> access it is before the transaction starts, not once it wants to read\n"
  "> out the buffer (unless we add more hacks to delay the start of a read\n"
  "> transaction until first buffer access...).  We'd be better off with a\n"
@@ -49,4 +54,4 @@
  ">\n"
  > -Scott
 
-11cccbeb670055d7b7abaa0cc42de3c25e9319932e3795440d2b99742dd50f5e
+51a6d1ea06be06848c9365dab9ed774f67a7c6078b011c31ab2270a7c85b47cb

diff --git a/a/content_digest b/N2/content_digest
index 2f009a4..68bbe5a 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -9,15 +9,15 @@
  "Subject\0Re: [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip\0"
  "Date\0Tue, 13 Dec 2011 10:46:51 +0800\0"
  "To\0Scott Wood <scottwood@freescale.com>\0"
- "Cc\0Artem.Bityutskiy@nokia.com"
-  dedekind1@gmail.com
-  linuxppc-dev@lists.ozlabs.org
-  linux-kernel@vger.kernel.org
-  shuo.liu@freescale.com
-  linux-mtd@lists.infradead.org
-  akpm@linux-foundation.org
-  leoli@freescale.com
- " dwmw2@infradead.org\0"
+ "Cc\0<dedekind1@gmail.com>"
+  <shuo.liu@freescale.com>
+  <dwmw2@infradead.org>
+  <Artem.Bityutskiy@nokia.com>
+  <linux-mtd@lists.infradead.org>
+  <linuxppc-dev@lists.ozlabs.org>
+  <akpm@linux-foundation.org>
+  <linux-kernel@vger.kernel.org>
+ " <leoli@freescale.com>\0"
  "\00:1\0"
  "b\0"
  "\344\272\216 2011\345\271\26412\346\234\21013\346\227\245 05:30, Scott Wood \345\206\231\351\201\223:\n"
@@ -49,4 +49,4 @@
  ">\n"
  > -Scott
 
-11cccbeb670055d7b7abaa0cc42de3c25e9319932e3795440d2b99742dd50f5e
+44f3103d9732604433fdc47eb9468c57c1abadda8e3f6bd00ac336684359f12a

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.