[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <28685183e34f3ae6839eb73265f9055f554ad6f1.1616971780.git.unixbhaskar@gmail.com>
Date: Mon, 29 Mar 2021 05:23:25 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: dmaengine@...r.kernel.org, dri-devel@...ts.freedesktop.org,
hch@....de, iommu@...ts.linux-foundation.org,
linuxppc-dev@...ts.ozlabs.org, dave.jiang@...el.com,
dan.j.williams@...el.com
Cc: Bhaskar Chowdhury <unixbhaskar@...il.com>, rdunlap@...radead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 29/30] edma.c: Fix a typo
s/transfering/transferring/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
drivers/dma/ti/edma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/ti/edma.c b/drivers/dma/ti/edma.c
index 35d81bd857f1..5ad771e34457 100644
--- a/drivers/dma/ti/edma.c
+++ b/drivers/dma/ti/edma.c
@@ -1815,7 +1815,7 @@ static void edma_issue_pending(struct dma_chan *chan)
* This limit exists to avoid a possible infinite loop when waiting for proof
* that a particular transfer is completed. This limit can be hit if there
* are large bursts to/from slow devices or the CPU is never able to catch
- * the DMA hardware idle. On an AM335x transfering 48 bytes from the UART
+ * the DMA hardware idle. On an AM335x transferring 48 bytes from the UART
* RX-FIFO, as many as 55 loops have been seen.
*/
#define EDMA_MAX_TR_WAIT_LOOPS 1000
--
2.26.3
Powered by blists - more mailing lists