From: Pavan Bobba <opensource206@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Pavan Bobba <opensource206@gmail.com>
Subject: [PATCH 00/11] Type encoding info dropped from variable and function names in NIC driver part2
Date: Tue, 31 Oct 2023 11:04:23 +0530 [thread overview]
Message-ID: <cover.1698730318.git.opensource206@gmail.com> (raw)
This patchset series consist of fixes to issues found by checkpatch
Pavan Bobba (11):
staging: vt6655: Type encoding info dropped from variable name
"qwBSSTimestamp"
staging: vt6655: Type encoding info dropped from variable name
"qwTSFOffset"
staging: vt6655: Type encoding info dropped from function name
"CARDqGetTSFOffset"
staging: vt6655: Type encoding info dropped from function name
"CARDbSetBeaconPeriod"
staging: vt6655: Type encoding info dropped from variable name
"wBeaconInterval"
staging: vt6655: Type encoding info dropped from variable name
"qwNextTBTT"
staging: vt6655: Type encoding info dropped from function name
"CARDqGetNextTBTT"
staging: vt6655: Type encoding info dropped from function name
"CARDbRadioPowerOff"
staging: vt6655: Type encoding info dropped from function name
"CARDvSafeResetTx"
staging: vt6655: Type encoding info dropped from variable name
"pCurrTD"
staging: vt6655: Type encoding info dropped from variable name
"apTailTD"
drivers/staging/vt6655/card.c | 90 ++++++++++++++--------------
drivers/staging/vt6655/card.h | 18 +++---
drivers/staging/vt6655/device.h | 4 +-
drivers/staging/vt6655/device_main.c | 18 +++---
drivers/staging/vt6655/rxtx.c | 2 +-
5 files changed, 66 insertions(+), 66 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-31 5:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 5:34 Pavan Bobba [this message]
2023-10-31 5:34 ` [PATCH 01/11] staging: vt6655: Type encoding info dropped from variable name "qwBSSTimestamp" Pavan Bobba
2023-10-31 5:34 ` [PATCH 02/11] staging: vt6655: Type encoding info dropped from variable name "qwTSFOffset" Pavan Bobba
2023-10-31 5:34 ` [PATCH 03/11] staging: vt6655: Type encoding info dropped from function name "CARDqGetTSFOffset" Pavan Bobba
2023-10-31 5:34 ` [PATCH 04/11] staging: vt6655: Type encoding info dropped from function name "CARDbSetBeaconPeriod" Pavan Bobba
2023-10-31 5:34 ` [PATCH 05/11] staging: vt6655: Type encoding info dropped from variable name "wBeaconInterval" Pavan Bobba
2023-10-31 5:34 ` [PATCH 06/11] staging: vt6655: Type encoding info dropped from variable name "qwNextTBTT" Pavan Bobba
2023-10-31 5:34 ` [PATCH 07/11] staging: vt6655: Type encoding info dropped from function name "CARDqGetNextTBTT" Pavan Bobba
2023-10-31 5:34 ` [PATCH 08/11] staging: vt6655: Type encoding info dropped from function name "CARDbRadioPowerOff" Pavan Bobba
2023-10-31 5:34 ` [PATCH 09/11] staging: vt6655: Type encoding info dropped from function name "CARDvSafeResetTx" Pavan Bobba
2023-10-31 5:34 ` [PATCH 10/11] staging: vt6655: Type encoding info dropped from variable name "pCurrTD" Pavan Bobba
2023-10-31 5:34 ` [PATCH 11/11] staging: vt6655: Type encoding info dropped from variable name "apTailTD" Pavan Bobba
2023-11-04 11:39 ` [PATCH 00/11] Type encoding info dropped from variable and function names in NIC driver part2 Philipp Hortmann
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.1698730318.git.opensource206@gmail.com \
--to=opensource206@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox