All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <53F5EF78.2050800@linutronix.de>

diff --git a/a/1.txt b/N1/1.txt
index 0522f28..d02e9a6 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 On 08/19/2014 05:12 PM, Vinod Koul wrote:
 >>
->>     desc = dmaengine_prep_slave_single(rxchan, …);
+>>     desc = dmaengine_prep_slave_single(rxchan, ?);
 >>     rx_cookie = dmaengine_submit(desc);
 >>     dma_async_issue_pending(rxchan);
 >>
@@ -31,7 +31,7 @@ But where is it written that the life time of the cookie is limited?
 Looking at the "cooking check" code there is no such thing. It is
 simply compare of completed vs passed number but okay, this is an
 implementation detail.
-From [0] it says under "4. Submit the transaction":
+>From [0] it says under "4. Submit the transaction":
 
 | This returns a cookie can be used to check the progress of DMA engine
 | activity via other DMA engine calls not covered in this document.
@@ -40,7 +40,7 @@ no life time limit mentioned here. Which brings to the question: Why is
 it okay to use the cookie after the transaction "terminated" normally
 but not if it has been canceled?
 
-And from [0] the API explanation  "4. … dma_async_is_tx_complete()":
+And from [0] the API explanation  "4. ? dma_async_is_tx_complete()":
 
 |Note:
 |    Not all DMA engine drivers can return reliable information for
@@ -78,7 +78,7 @@ dw/core.c. That one does cookie complete on terminate:
  dwc_control(DMA_TERMINATE_ALL) -> dwc_descriptor_complete() ->
  dma_cookie_complete().
 
-That is why it works for them…
+That is why it works for them?
 
 [0] Documentation/dmaengine.txt
 
@@ -87,7 +87,3 @@ That is why it works for them…
 > 
 
 Sebastian
---
-To unsubscribe from this list: send the line "unsubscribe linux-serial" 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 27967ea..9852a61 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,24 +3,15 @@
  "ref\020140731121702.GU8181@intel.com\0"
  "ref\020140808162950.GA12080@linutronix.de\0"
  "ref\020140819151216.GO13288@intel.com\0"
- "From\0Sebastian Andrzej Siewior <bigeasy@linutronix.de>\0"
- "Subject\0Re: [PATCH 1/7] dmaengine: edma: fix two faults which happen with the 8250_dma user\0"
+ "From\0bigeasy@linutronix.de (Sebastian Andrzej Siewior)\0"
+ "Subject\0[PATCH 1/7] dmaengine: edma: fix two faults which happen with the 8250_dma user\0"
  "Date\0Thu, 21 Aug 2014 15:09:12 +0200\0"
- "To\0Vinod Koul <vinod.koul@intel.com>\0"
- "Cc\0linux-serial@vger.kernel.org"
-  linux-kernel@vger.kernel.org
-  linux-omap@vger.kernel.org
-  linux-arm-kernel@lists.infradead.org
-  tony@atomide.com
-  balbi@ti.com
-  Joel Fernandes <joelf@ti.com>
-  Dan Williams <dan.j.williams@intel.com>
- " dmaengine@vger.kernel.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 08/19/2014 05:12 PM, Vinod Koul wrote:\n"
  ">>\n"
- ">>     desc = dmaengine_prep_slave_single(rxchan, \342\200\246);\n"
+ ">>     desc = dmaengine_prep_slave_single(rxchan, ?);\n"
  ">>     rx_cookie = dmaengine_submit(desc);\n"
  ">>     dma_async_issue_pending(rxchan);\n"
  ">>\n"
@@ -51,7 +42,7 @@
  "Looking at the \"cooking check\" code there is no such thing. It is\n"
  "simply compare of completed vs passed number but okay, this is an\n"
  "implementation detail.\n"
- "From [0] it says under \"4. Submit the transaction\":\n"
+ ">From [0] it says under \"4. Submit the transaction\":\n"
  "\n"
  "| This returns a cookie can be used to check the progress of DMA engine\n"
  "| activity via other DMA engine calls not covered in this document.\n"
@@ -60,7 +51,7 @@
  "it okay to use the cookie after the transaction \"terminated\" normally\n"
  "but not if it has been canceled?\n"
  "\n"
- "And from [0] the API explanation  \"4. \342\200\246 dma_async_is_tx_complete()\":\n"
+ "And from [0] the API explanation  \"4. ? dma_async_is_tx_complete()\":\n"
  "\n"
  "|Note:\n"
  "|    Not all DMA engine drivers can return reliable information for\n"
@@ -98,7 +89,7 @@
  " dwc_control(DMA_TERMINATE_ALL) -> dwc_descriptor_complete() ->\n"
  " dma_cookie_complete().\n"
  "\n"
- "That is why it works for them\342\200\246\n"
+ "That is why it works for them?\n"
  "\n"
  "[0] Documentation/dmaengine.txt\n"
  "\n"
@@ -106,10 +97,6 @@
  "> Thanks\n"
  "> \n"
  "\n"
- "Sebastian\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-serial\" in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ Sebastian
 
-7b731ee95475ae675ccfc337b9b9c80e2fa5b9e1aa7b35e6f26d22bda0a48fe1
+87d88b0119d993a96e8805f49c3b940251445909fc131a3430ccf05fc54b343d

diff --git a/a/1.txt b/N2/1.txt
index 0522f28..7b2e1e5 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -31,7 +31,7 @@ But where is it written that the life time of the cookie is limited?
 Looking at the "cooking check" code there is no such thing. It is
 simply compare of completed vs passed number but okay, this is an
 implementation detail.
-From [0] it says under "4. Submit the transaction":
+>From [0] it says under "4. Submit the transaction":
 
 | This returns a cookie can be used to check the progress of DMA engine
 | activity via other DMA engine calls not covered in this document.
@@ -87,7 +87,3 @@ That is why it works for them…
 > 
 
 Sebastian
---
-To unsubscribe from this list: send the line "unsubscribe linux-serial" 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/N2/content_digest
index 27967ea..e886a97 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -51,7 +51,7 @@
  "Looking at the \"cooking check\" code there is no such thing. It is\n"
  "simply compare of completed vs passed number but okay, this is an\n"
  "implementation detail.\n"
- "From [0] it says under \"4. Submit the transaction\":\n"
+ ">From [0] it says under \"4. Submit the transaction\":\n"
  "\n"
  "| This returns a cookie can be used to check the progress of DMA engine\n"
  "| activity via other DMA engine calls not covered in this document.\n"
@@ -106,10 +106,6 @@
  "> Thanks\n"
  "> \n"
  "\n"
- "Sebastian\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-serial\" in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ Sebastian
 
-7b731ee95475ae675ccfc337b9b9c80e2fa5b9e1aa7b35e6f26d22bda0a48fe1
+6761cf2666c6af6cf713bde405cf552f02b818bf8166e5b298da9cfc5d843643

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.