From: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
To: outreachy@lists.linux.dev
Cc: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
Subject: [PATCH v2 0/4]: staging: vt6655: Rename variable bUpdateBBVGA, byCurrentCh, byCurPwr and byBBPreEDRSSI
Date: Tue, 17 Oct 2023 11:34:01 +0100 [thread overview]
Message-ID: <cover.1697535791.git.gilbertadikankwu@gmail.com> (raw)
Make the variable names adhere to Linux kernel coding style and fix
checkpatch.pl errors.
v1 -> v2:
fix error reported here [here](https://lore.kernel.org/outreachy/d77f35a3-5eec-d02f-459b-1968a58ff7d5@intel.com/T/#m12a562e40fc6c250f6989b252c7e121435c48bc2)
reword the commit messages as suggested [here](https://lore.kernel.org/outreachy/d77f35a3-5eec-d02f-459b-1968a58ff7d5@intel.com/T/#m9051ff56ac0248bbcad371c82e23cc22cefb2a23)
Gilbert Adikankwu (4):
staging: vt6655: Rename variable bUpdateBBVGA
staging: vt6655: Rename variable byCurrentCh
staging: vt6655: Rename variable byCurPwr
staging: vt6655: Rename variable byBBPreEDRSSI
drivers/staging/vt6655/baseband.c | 2 +-
drivers/staging/vt6655/channel.c | 18 +++++++++---------
drivers/staging/vt6655/device.h | 8 ++++----
drivers/staging/vt6655/device_main.c | 8 ++++----
drivers/staging/vt6655/dpc.c | 2 +-
drivers/staging/vt6655/rf.c | 4 ++--
6 files changed, 21 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-17 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 10:34 Gilbert Adikankwu [this message]
2023-10-17 10:34 ` [PATCH v2 1/4] staging: vt6655: Rename variable bUpdateBBVGA Gilbert Adikankwu
2023-10-17 10:34 ` [PATCH v2 2/4] staging: vt6655: Rename variable byCurrentCh Gilbert Adikankwu
2023-10-17 10:34 ` [PATCH v2 3/4] staging: vt6655: Rename variable byCurPwr Gilbert Adikankwu
2023-10-17 10:34 ` [PATCH v2 4/4] staging: vt6655: Rename variable byBBPreEDRSSI Gilbert Adikankwu
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=cover.1697535791.git.gilbertadikankwu@gmail.com \
--to=gilbertadikankwu@gmail.com \
--cc=outreachy@lists.linux.dev \
/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.