From: Pavan Bobba <opensource206@gmail.com>
To: Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
Philipp Hortmann <philipp.g.hortmann@gmail.com>,
outreachy@lists.linux.dev
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v2] staging: vt6655: replace camel case by snake case
Date: Sat, 5 Aug 2023 14:29:04 +0530 [thread overview]
Message-ID: <ZM4PWL55pMQiYIX6@ubuntu.myguest.virtualbox.org> (raw)
Replace array name of camel case by snake case. Issue found
by checkpatch
Signed-off-by: Pavan Bobba <opensource206@gmail.com>
---
v1 -> v2: 1.character '_' added in the array name "byvt3253b0_rfmde"
2. typo in the subject line "small case" corrected with the
proper word "snake case"
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 0e135af8316b..8b913c64845c 100644
--- a/drivers/staging/vt6655/baseband.c
+++ b/drivers/staging/vt6655/baseband.c
@@ -499,7 +499,7 @@ static const unsigned char by_vt3253_init_tab_rfmd[CB_VT3253_INIT_FOR_RFMD][2] =
};
#define CB_VT3253B0_INIT_FOR_RFMD 256
-static const unsigned char byVT3253B0_RFMD[CB_VT3253B0_INIT_FOR_RFMD][2] = {
+static const unsigned char byvt3253b0_rfmd[CB_VT3253B0_INIT_FOR_RFMD][2] = {
{0x00, 0x31},
{0x01, 0x00},
{0x02, 0x00},
@@ -2005,8 +2005,8 @@ bool bb_vt3253_init(struct vnt_private *priv)
} else {
for (ii = 0; ii < CB_VT3253B0_INIT_FOR_RFMD; ii++)
result &= bb_write_embedded(priv,
- byVT3253B0_RFMD[ii][0],
- byVT3253B0_RFMD[ii][1]);
+ byvt3253b0_rfmd[ii][0],
+ byvt3253b0_rfmd[ii][1]);
for (ii = 0; ii < CB_VT3253B0_AGC_FOR_RFMD2959; ii++)
result &= bb_write_embedded(priv,
--
2.34.1
next reply other threads:[~2023-08-05 8:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 8:59 Pavan Bobba [this message]
2023-08-05 16:30 ` [PATCH v2] staging: vt6655: replace camel case by snake case Dan Carpenter
2023-08-09 12:20 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 12:53 Pavan Bobba
2023-08-23 12:58 ` Julia Lawall
2023-08-23 13:32 ` Pavan Bobba
2023-08-23 13:58 ` Greg KH
2023-08-09 12:47 Pavan Bobba
2023-08-11 21:27 ` Greg KH
2023-08-12 18:29 ` Pavan Bobba
2023-08-12 18:41 ` Julia Lawall
2023-08-14 13:02 ` Pavan Bobba
2023-08-14 15:20 ` Greg KH
2023-08-17 12:08 ` Pavan Bobba
2023-08-02 13:26 [PATCH] staging: vt6655: replace camel case by small case Pavan Bobba
2023-08-02 13:33 ` Dan Carpenter
2023-08-04 11:53 ` [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-04 12:01 ` Dan Carpenter
2023-08-04 13:22 ` Greg Kroah-Hartman
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=ZM4PWL55pMQiYIX6@ubuntu.myguest.virtualbox.org \
--to=opensource206@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=straube.linux@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;
as well as URLs for NNTP newsgroup(s).