[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20210508072156.GA14656@user>
Date: Sat, 8 May 2021 12:51:56 +0530
From: Saurav Girepunje <saurav.girepunje@...il.com>
To: b-liu@...com, gregkh@...uxfoundation.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: saurav.girepunje@...mail.com
Subject: [PATCH] usb: musb: Fix spelling mistake "tranfer" -> "transfer"
Fix spelling mistake "tranfer" -> "transfer" in musb_gadget.c file.
Signed-off-by: Saurav Girepunje <saurav.girepunje@...il.com>
---
drivers/usb/musb/musb_gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
index f62ffaede1ab..0246194d5577 100644
--- a/drivers/usb/musb/musb_gadget.c
+++ b/drivers/usb/musb/musb_gadget.c
@@ -611,7 +611,7 @@ static void rxstate(struct musb *musb, struct musb_request *req)
* mode 0 only. So we do not get endpoint interrupts due to DMA
* completion. We only get interrupts from DMA controller.
*
- * We could operate in DMA mode 1 if we knew the size of the tranfer
+ * We could operate in DMA mode 1 if we knew the size of the transfer
* in advance. For mass storage class, request->length = what the host
* sends, so that'd work. But for pretty much everything else,
* request->length is routinely more than what the host sends. For
--
2.25.1
Powered by blists - more mailing lists