From: Daniel Cashman <dan.a.cashman@gmail.com>
To: gregkh@linuxfoundation.org
Cc: forest@alittletooquiet.net, dan.a.cashman@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [Patch v2 3/3] staging: vt6656: Split arguments to avoid 80-char violation in rf.c
Date: Sun, 2 Apr 2017 13:48:12 -0700 [thread overview]
Message-ID: <1491166092-3235-4-git-send-email-dan.a.cashman@gmail.com> (raw)
In-Reply-To: <1491166092-3235-3-git-send-email-dan.a.cashman@gmail.com>
From: Dan Cashman <dan.a.cashman@gmail.com>
Wrap arguments of call to vnt_control_out() to avoid exceeding 80
character limit, but maintain alignment.
Signed-off-by: Daniel Cashman <dan.a.cashman@gmail.com>
---
drivers/staging/vt6656/rf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/vt6656/rf.c b/drivers/staging/vt6656/rf.c
index d157e5c..23581af 100644
--- a/drivers/staging/vt6656/rf.c
+++ b/drivers/staging/vt6656/rf.c
@@ -937,7 +937,8 @@ void vnt_rf_table_download(struct vnt_private *priv)
memcpy(array, addr2, length);
vnt_control_out(priv, MESSAGE_TYPE_WRITE,
- value, MESSAGE_REQUEST_RF_CH2, length, array);
+ value, MESSAGE_REQUEST_RF_CH2,
+ length, array);
length2 -= length;
value += length;
--
2.7.4
prev parent reply other threads:[~2017-04-02 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 3:29 [PATCH] staging: vt6656: Fix spaces, char limit and embedded func name in print Daniel Cashman
2017-04-02 6:02 ` Greg KH
2017-04-02 20:48 ` [Patch v2 0/3] staging: vt6656: Fix checkpatch style violations Daniel Cashman
2017-04-02 20:48 ` [Patch v2 1/3] staging: vt6656: convert spaces to tabs for rf.c Daniel Cashman
2017-04-02 20:48 ` [Patch v2 2/3] staging: vt6656: Replace embedded function name with __func__ in rf.c Daniel Cashman
2017-04-02 20:48 ` Daniel Cashman [this message]
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=1491166092-3235-4-git-send-email-dan.a.cashman@gmail.com \
--to=dan.a.cashman@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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