[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200728182610.2538-1-dhiraj.sharma0024@gmail.com>
Date: Tue, 28 Jul 2020 23:56:10 +0530
From: Dhiraj Sharma <dhiraj.sharma0024@...il.com>
To: manishc@...vell.com, gregkh@...uxfoundation.org
Cc: Dhiraj Sharma <dhiraj.sharma0024@...il.com>,
netdev@...r.kernel.org, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] staging: qlge: qlge_dbg: removed comment repition
Inside function ql_get_dump comment statement had a repition of word
"to" which I removed and checkpatch.pl ouputs zero error or warnings
now.
Signed-off-by: Dhiraj Sharma <dhiraj.sharma0024@...il.com>
---
drivers/staging/qlge/qlge_dbg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/qlge/qlge_dbg.c b/drivers/staging/qlge/qlge_dbg.c
index 985a6c341294..a55bf0b3e9dc 100644
--- a/drivers/staging/qlge/qlge_dbg.c
+++ b/drivers/staging/qlge/qlge_dbg.c
@@ -1298,7 +1298,7 @@ void ql_get_dump(struct ql_adapter *qdev, void *buff)
* If the dump has already been taken and is stored
* in our internal buffer and if force dump is set then
* just start the spool to dump it to the log file
- * and also, take a snapshot of the general regs to
+ * and also, take a snapshot of the general regs
* to the user's buffer or else take complete dump
* to the user's buffer if force is not set.
*/
--
2.17.1
Powered by blists - more mailing lists