All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <560A0B4C.90206@ti.com>

diff --git a/a/1.txt b/N1/1.txt
index 57b70e2..9ec0397 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -14,7 +14,7 @@ On Monday 28 September 2015 10:05 PM, Paul Walmsley wrote:
 > 
 > Looks pretty good.  I'm slightly concerned about the latency jitter impact 
 > on -rt kernels for that local_irq_disable() section.  Looks like it could 
-> hold off interrupts for ~(50 udelay µs) + 50*((RTC register read time) + 
+> hold off interrupts for ~(50 udelay ?s) + 50*((RTC register read time) + 
 > 1).  But I'm not sure if preempt_enable/disable() is a good alternative 
 > since a bunch of interrupt top halves could conceivably run after the RTC 
 > goes non-busy and result in the RTC not being locked/unlocked. 
diff --git a/a/content_digest b/N1/content_digest
index 06d9634..3c23f1f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,16 +2,10 @@
  "ref\055DE9055.4090701@ti.com\0"
  "ref\056037FEA.5070807@ti.com\0"
  "ref\0alpine.DEB.2.02.1509280822250.7947@utopia.booyaka.com\0"
- "From\0Lokesh Vutla <a0131933@ti.com>\0"
- "Subject\0Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks\0"
+ "From\0a0131933@ti.com (Lokesh Vutla)\0"
+ "Subject\0[PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks\0"
  "Date\0Tue, 29 Sep 2015 09:23:48 +0530\0"
- "To\0Paul Walmsley <paul@pwsan.com>\0"
- "Cc\0Lokesh Vutla <lokeshvutla@ti.com>"
-  nsekhar@ti.com
-  t-kristo@ti.com
-  tony@atomide.com
-  linux-omap@vger.kernel.org
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hi Paul,\n"
@@ -30,7 +24,7 @@
  "> \n"
  "> Looks pretty good.  I'm slightly concerned about the latency jitter impact \n"
  "> on -rt kernels for that local_irq_disable() section.  Looks like it could \n"
- "> hold off interrupts for ~(50 udelay \302\265s) + 50*((RTC register read time) + \n"
+ "> hold off interrupts for ~(50 udelay ?s) + 50*((RTC register read time) + \n"
  "> 1).  But I'm not sure if preempt_enable/disable() is a good alternative \n"
  "> since a bunch of interrupt top halves could conceivably run after the RTC \n"
  "> goes non-busy and result in the RTC not being locked/unlocked. \n"
@@ -54,4 +48,4 @@
  "Thanks and regards,\n"
  Lokesh
 
-11bbdf88b89bbccb9972d016db1b477308f7e462a2adef390f56e8fcfea22944
+f629b6f29e238e6f7d050017243c7230611c9f4d8d41a6f5e0aed2244dd4da18

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.