From: Nadim Almas <nadim.902@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, markh@compro.net,
linux-kernel@vger.kernel.org
Subject: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue
Date: Fri, 30 Sep 2016 14:49:12 -0700 [thread overview]
Message-ID: <20160930214912.GA6932@gmail.com> (raw)
Fixed coding style issue.
Signed-off-by: Nadim Almas <nadim.902@gmail.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
next reply other threads:[~2016-09-30 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 21:49 Nadim Almas [this message]
2016-10-02 15:23 ` Greg KH
[not found] ` <CANQNnfGy50kygxezO3WEt+zHh5EH5RRgvKkJA0OFU7BFPMn5KQ@mail.gmail.com>
[not found] ` <20161002153937.GA21118@kroah.com>
2016-10-02 15:43 ` Fwd: " Nadim Almas
2016-10-02 16:09 ` Greg KH
2016-10-02 16:41 ` Nadim Almas
2016-10-02 17:49 ` Greg KH
2016-10-05 21:53 Nadim Almas
2016-10-06 5:21 ` Greg KH
2016-10-06 8:22 ` Nadim Almas
2016-10-06 15:23 ` Nadim Almas
2016-10-06 15:52 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160930214912.GA6932@gmail.com \
--to=nadim.902@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome