From: Tommaso Merciai <tomm.merciai@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: tomm.merciai@gmail.com, Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lucas Henneman <lucas.henneman@linaro.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/3] staging: vt6655: replace camel case variables
Date: Tue, 5 Oct 2021 22:56:56 +0200 [thread overview]
Message-ID: <20211005205702.14029-1-tomm.merciai@gmail.com> (raw)
This series replace the following camel case variables into
equivalent snake case variable for vt6655 driver.
bShortSlotTime -> short_slot_time
ldBmThreshold -> dbm_threshold
PortOffset -> port_offset
Tommaso Merciai (3):
staging: vt6655: fix camelcase in bShortSlotTime
staging: vt6655: fix camelcase in ldBmThreshold
staging: vt6655: fix camelcase in PortOffset
drivers/staging/vt6655/baseband.c | 58 +++++------
drivers/staging/vt6655/card.c | 90 ++++++++--------
drivers/staging/vt6655/channel.c | 10 +-
drivers/staging/vt6655/device.h | 6 +-
drivers/staging/vt6655/device_main.c | 150 +++++++++++++--------------
drivers/staging/vt6655/mac.c | 46 ++++----
drivers/staging/vt6655/power.c | 24 ++---
drivers/staging/vt6655/rf.c | 12 +--
drivers/staging/vt6655/rxtx.c | 12 +--
9 files changed, 204 insertions(+), 204 deletions(-)
--
2.25.1
next reply other threads:[~2021-10-05 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 20:56 Tommaso Merciai [this message]
2021-10-05 20:56 ` [PATCH v7 1/3] staging: vt6655: fix camelcase in bShortSlotTime Tommaso Merciai
2021-10-06 8:09 ` Dan Carpenter
2021-10-07 7:10 ` Tommaso Merciai
2021-10-05 20:56 ` [PATCH v7 2/3] staging: vt6655: fix camelcase in ldBmThreshold Tommaso Merciai
2021-10-05 20:56 ` [PATCH v7 3/3] staging: vt6655: fix camelcase in PortOffset Tommaso Merciai
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=20211005205702.14029-1-tomm.merciai@gmail.com \
--to=tomm.merciai@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lucas.henneman@linaro.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;
as well as URLs for NNTP newsgroup(s).