[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160930214912.GA6932@gmail.com>
Date: Fri, 30 Sep 2016 14:49:12 -0700
From: Nadim Almas <nadim.902@...il.com>
To: gregkh@...uxfoundation.org
Cc: devel@...verdev.osuosl.org, markh@...pro.net,
linux-kernel@...r.kernel.org
Subject: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding
style issue
Fixed coding style issue.
Signed-off-by: Nadim Almas <nadim.902@...il.com>
---
drivers/staging/dgnc/dgnc_neo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c
index e794056..bc15584 100644
--- a/drivers/staging/dgnc/dgnc_neo.c
+++ b/drivers/staging/dgnc/dgnc_neo.c
@@ -554,7 +554,8 @@ static inline void neo_parse_lsr(struct dgnc_board *brd, uint port)
* Rx Oruns. Exar says that an orun will NOT corrupt
* the FIFO. It will just replace the holding register
* with this new data byte. So basically just ignore this.
- * Probably we should eventually have an orun stat in our driver...
+ * Probably we should eventually have an orun stat in our
+ * driver...
*/
ch->ch_err_overrun++;
}
--
2.7.4
Powered by blists - more mailing lists