From: Arjun Krishna Babu <arjunkrishnababu96@gmail.com>
To: forest@alittletooquiet.net
Cc: gregkh@linuxfoundation.org, tvboxspy@gmail.com, ewk@edkovsky.org,
himani93@gmail.com, dilekuzulmez@gmail.com,
sakshi.april5@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Arjun Krishna Babu <arjunkrishnababu96@gmail.com>
Subject: [PATCH] staging: vt6655: Fixed two lines over 80 characters long
Date: Wed, 30 Sep 2015 18:24:22 +0530 [thread overview]
Message-ID: <1443617662-12805-1-git-send-email-arjunkrishnababu96@gmail.com> (raw)
Two lines of code that were over 80 characters long is fixed
by splitting them across multiple lines.
The lines of code are now easier to comprehend.
Issue found by checkpatch.
Signed-off-by: Arjun Krishna Babu <arjunkrishnababu96@gmail.com>
---
drivers/staging/vt6655/baseband.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
index 9e61f2d..1e6c0c4 100644
--- a/drivers/staging/vt6655/baseband.c
+++ b/drivers/staging/vt6655/baseband.c
@@ -2089,9 +2089,19 @@ bool BBbVT3253Init(struct vnt_private *priv)
byVT3253B0_UW2451[ii][0],
byVT3253B0_UW2451[ii][1]);
- /* Init ANT B select,TX Config CR09 = 0x61->0x45, 0x45->0x41(VC1/VC2 define, make the ANT_A, ANT_B inverted) */
+ /* Init ANT B select,
+ * TX Config CR09 = 0x61->0x45,
+ * 0x45->0x41(VC1/VC2 define, make the ANT_A, ANT_B inverted)
+ */
+
/*bResult &= BBbWriteEmbedded(dwIoBase,0x09,0x41);*/
- /* Init ANT B select,RX Config CR10 = 0x28->0x2A, 0x2A->0x28(VC1/VC2 define, make the ANT_A, ANT_B inverted) */
+
+ /* Init ANT B select,
+ * RX Config CR10 = 0x28->0x2A,
+ * 0x2A->0x28(VC1/VC2 define,
+ * make the ANT_A, ANT_B inverted)
+ */
+
/*bResult &= BBbWriteEmbedded(dwIoBase,0x0a,0x28);*/
/* Select VC1/VC2, CR215 = 0x02->0x06 */
bResult &= BBbWriteEmbedded(priv, 0xd7, 0x06);
--
1.9.1
reply other threads:[~2015-09-30 12:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1443617662-12805-1-git-send-email-arjunkrishnababu96@gmail.com \
--to=arjunkrishnababu96@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilekuzulmez@gmail.com \
--cc=ewk@edkovsky.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=himani93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sakshi.april5@gmail.com \
--cc=tvboxspy@gmail.com \
/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
all inboxes | Powered by JetHome®