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

diff --git a/a/1.txt b/N1/1.txt
index c91757d..5b8048f 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,23 +1,18 @@
 On Wednesday 10 September 2008, David Miller wrote:
-> >=20
-> > I don't think anyone in particular has been _pushing_ to resolve th=
-ese
-> > NTP related issues ... lack of urgency. =A0Maybe it's fair to think=
- of
-> > that as a process issue. =A0If DaveM wants SPARC64 to completely re=
-move
-> > its legacy RTC support for some release (which?) then: =A0(a) great=
-! and
+> > 
+> > I don't think anyone in particular has been _pushing_ to resolve these
+> > NTP related issues ... lack of urgency.  Maybe it's fair to think of
+> > that as a process issue.  If DaveM wants SPARC64 to completely remove
+> > its legacy RTC support for some release (which?) then:  (a) great! and
 > > (b) that should be sufficient urgency.
->=20
+> 
 > Well, firstly my RTC sparc work is 2.6.28 targetted.
 
-=46ine; Andrew and Thomas won't need to worry about this patch
+Fine; Andrew and Thomas won't need to worry about this patch
 for now, then.
 
 
-> Secondly, that sleeping capability is only really needed for I2C base=
-d
+> Secondly, that sleeping capability is only really needed for I2C based
 > RTC chips, of which sparc isn't currently making any use of.
 
 Not quite right.  The RTC calls you make grabs a mutex; *ALL* calls
@@ -31,8 +26,3 @@ Someone running Linux on one of the FPGA-based SPARCs might well
 use an I2C based RTC though.
 
 - 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 7b2a9d7..21380da 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -16,25 +16,20 @@
  "\00:1\0"
  "b\0"
  "On Wednesday 10 September 2008, David Miller wrote:\n"
- "> >=20\n"
- "> > I don't think anyone in particular has been _pushing_ to resolve th=\n"
- "ese\n"
- "> > NTP related issues ... lack of urgency. =A0Maybe it's fair to think=\n"
- " of\n"
- "> > that as a process issue. =A0If DaveM wants SPARC64 to completely re=\n"
- "move\n"
- "> > its legacy RTC support for some release (which?) then: =A0(a) great=\n"
- "! and\n"
+ "> > \n"
+ "> > I don't think anyone in particular has been _pushing_ to resolve these\n"
+ "> > NTP related issues ... lack of urgency. \302\240Maybe it's fair to think of\n"
+ "> > that as a process issue. \302\240If DaveM wants SPARC64 to completely remove\n"
+ "> > its legacy RTC support for some release (which?) then: \302\240(a) great! and\n"
  "> > (b) that should be sufficient urgency.\n"
- ">=20\n"
+ "> \n"
  "> Well, firstly my RTC sparc work is 2.6.28 targetted.\n"
  "\n"
- "=46ine; Andrew and Thomas won't need to worry about this patch\n"
+ "Fine; Andrew and Thomas won't need to worry about this patch\n"
  "for now, then.\n"
  "\n"
  "\n"
- "> Secondly, that sleeping capability is only really needed for I2C base=\n"
- "d\n"
+ "> Secondly, that sleeping capability is only really needed for I2C based\n"
  "> RTC chips, of which sparc isn't currently making any use of.\n"
  "\n"
  "Not quite right.  The RTC calls you make grabs a mutex; *ALL* calls\n"
@@ -47,11 +42,6 @@
  "Someone running Linux on one of the FPGA-based SPARCs might well\n"
  "use an I2C based RTC though.\n"
  "\n"
- "- Dave\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
 
-c073b44847a4be7245662c71eba5fe1b7e955b24d56261b258e9e3fc0fc7ffb3
+bdcf9840c988a2baf1721c8531496e211ad97737bb2027900c0cc9f2b318d2ee

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.