From: Varsha Rao <rvarsha016@gmail.com>
To: outreachy-kernel@googlegroups.com, forest@alittletooquiet.net,
gregkh@linuxfoundation.org
Cc: rvarsha016@gmail.com
Subject: [PATCH] Staging: vt6655: Replace byVT3253InitTab_RFMD with byvt3253inittab_rfmd
Date: Sat, 8 Oct 2016 23:33:35 +0530 [thread overview]
Message-ID: <20161008180335.GA5425@euri> (raw)
This patch fixes the patchcheck issue of CamelCase.This
is done by replacing byVT3253InitTab_RFMD with
byvt3253inittab_rfmd.
Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
---
drivers/staging/vt6655/baseband.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
index e739ecc..ff96c5e 100644
--- a/drivers/staging/vt6655/baseband.c
+++ b/drivers/staging/vt6655/baseband.c
@@ -68,7 +68,7 @@
/*--------------------- Static Variables --------------------------*/
#define CB_VT3253_INIT_FOR_RFMD 446
-static const unsigned char byVT3253InitTab_RFMD[CB_VT3253_INIT_FOR_RFMD][2] = {
+static const unsigned char byvt3253inittab_rfmd[CB_VT3253_INIT_FOR_RFMD][2] = {
{0x00, 0x30},
{0x01, 0x00},
{0x02, 0x00},
@@ -2022,8 +2022,8 @@ bool BBbVT3253Init(struct vnt_private *priv)
if (byLocalID <= REV_ID_VT3253_A1) {
for (ii = 0; ii < CB_VT3253_INIT_FOR_RFMD; ii++)
bResult &= BBbWriteEmbedded(priv,
- byVT3253InitTab_RFMD[ii][0],
- byVT3253InitTab_RFMD[ii][1]);
+ byvt3253inittab_rfmd[ii][0],
+ byvt3253inittab_rfmd[ii][1]);
} else {
for (ii = 0; ii < CB_VT3253B0_INIT_FOR_RFMD; ii++)
--
2.7.4
next reply other threads:[~2016-10-08 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 18:03 Varsha Rao [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-08 14:33 [PATCH] Staging: vt6655: Replace byVT3253InitTab_RFMD with BYVT3253INITTAB_RFMD Varsha Rao
2016-10-08 14:36 ` Greg KH
2016-10-08 14:50 ` Varsha Rao
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=20161008180335.GA5425@euri \
--to=rvarsha016@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.