All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <200809081632.26166.david-b@pacbell.net>

diff --git a/a/1.txt b/N1/1.txt
index ab493b8..2d76b41 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,13 +1,11 @@
 On Monday 08 September 2008, James Bottomley wrote:
->=20
+> 
 > > All the powerpc folks are doing is providing a dummy shim into the
-> > RTC layer using their machine description vector, and not really us=
-ing
+> > RTC layer using their machine description vector, and not really using
 > > the RTC layer drivers at all.
->=20
-> But realistically that's all we need. =A0Our RTC is controlled by two
-> calls into firmware: a get and a set; nothing else. =A0We don't have =
-the
+> 
+> But realistically that's all we need.  Our RTC is controlled by two
+> calls into firmware: a get and a set; nothing else.  We don't have the
 > docs to get at the clock without the firmware calls.
 
 True for PARISC ... but not for PowerPC.  Lots of PowerPC
@@ -15,9 +13,3 @@ system boards use off-the-shelf RTCs with more capabilities
 than the machine description vector acknowledges.
 
 - Dave
-
---
-To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
- in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index c0fde63..8ac8045 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -13,27 +13,19 @@
  "\00:1\0"
  "b\0"
  "On Monday 08 September 2008, James Bottomley wrote:\n"
- ">=20\n"
+ "> \n"
  "> > All the powerpc folks are doing is providing a dummy shim into the\n"
- "> > RTC layer using their machine description vector, and not really us=\n"
- "ing\n"
+ "> > RTC layer using their machine description vector, and not really using\n"
  "> > the RTC layer drivers at all.\n"
- ">=20\n"
- "> But realistically that's all we need. =A0Our RTC is controlled by two\n"
- "> calls into firmware: a get and a set; nothing else. =A0We don't have =\n"
- "the\n"
+ "> \n"
+ "> But realistically that's all we need. \302\240Our RTC is controlled by two\n"
+ "> calls into firmware: a get and a set; nothing else. \302\240We don't have the\n"
  "> docs to get at the clock without the firmware calls.\n"
  "\n"
  "True for PARISC ... but not for PowerPC.  Lots of PowerPC\n"
  "system boards use off-the-shelf RTCs with more capabilities\n"
  "than the machine description vector acknowledges.\n"
  "\n"
- "- Dave\n"
- "\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-parisc\"=\n"
- " in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ - Dave
 
-a7f73ae980a5ac46788711aaa0bdb3dec0d5c9faab6a6ca57cda6503de39a648
+dd9fd21fe483f0406dff0ff3f864117d42b110790ac69ad777c7756a7432050b

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.