From: Selvakumar Elangovan <selvakumar16197@gmail.com>
To: forest@alittletooquiet.net, gregkh@linuxfoundation.org,
tvboxspy@gmail.com, oscar.carter@gmx.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH] staging: vt6656: fixed a CamelCase coding style issue.
Date: Fri, 19 Feb 2021 15:28:35 +0530 [thread overview]
Message-ID: <20210219095835.9687-1-selvakumar16197@gmail.com> (raw)
This patch renames CamelCase macros uVar and uModulo into u_var and
u_module in device.h
This issue was reported by checkpatch.pl
Signed-off-by: Selvakumar Elangovan <selvakumar16197@gmail.com>
---
drivers/staging/vt6656/device.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/vt6656/device.h b/drivers/staging/vt6656/device.h
index 947530fefe94..6615d356f74a 100644
--- a/drivers/staging/vt6656/device.h
+++ b/drivers/staging/vt6656/device.h
@@ -385,11 +385,11 @@ struct vnt_private {
struct ieee80211_low_level_stats low_stats;
};
-#define ADD_ONE_WITH_WRAP_AROUND(uVar, uModulo) { \
- if ((uVar) >= ((uModulo) - 1)) \
- (uVar) = 0; \
+#define ADD_ONE_WITH_WRAP_AROUND(u_var, u_modulo) { \
+ if ((u_var) >= ((u_modulo) - 1)) \
+ (u_var) = 0; \
else \
- (uVar)++; \
+ (u_var)++; \
}
int vnt_init(struct vnt_private *priv);
--
2.17.1
next reply other threads:[~2021-02-19 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 9:58 Selvakumar Elangovan [this message]
2021-02-19 10:40 ` [PATCH] staging: vt6656: fixed a CamelCase coding style issue Greg KH
2021-02-19 12:12 ` Dan Carpenter
2021-02-19 12:20 ` Selvakumar E
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=20210219095835.9687-1-selvakumar16197@gmail.com \
--to=selvakumar16197@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar.carter@gmx.com \
--cc=tvboxspy@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).