From: Jaya Durga <jayad@cdac.in>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Jaya Durga <jayad@cdac.in>
Subject: [PATCH 5/5] Staging: rtl8712: ieee80211: fixed camelcase coding style issue
Date: Sat, 20 May 2017 23:26:17 +0530 [thread overview]
Message-ID: <1495302977-26774-1-git-send-email-jayad@cdac.in> (raw)
Fixed coding style issue
Renamed cap_ShortPremble to cap_short_premble
Signed-off-by: Jaya Durga <jayad@cdac.in>
---
drivers/staging/rtl8712/ieee80211.c | 2 +-
drivers/staging/rtl8712/wifi.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8712/ieee80211.c b/drivers/staging/rtl8712/ieee80211.c
index a7152df..7196464 100644
--- a/drivers/staging/rtl8712/ieee80211.c
+++ b/drivers/staging/rtl8712/ieee80211.c
@@ -182,7 +182,7 @@ int r8712_generate_ie(struct registry_priv *pregistrypriv)
*(u16 *)ie = 0;
*(__le16 *)ie |= cpu_to_le16(cap_IBSS);
if (pregistrypriv->preamble == PREAMBLE_SHORT)
- *(__le16 *)ie |= cpu_to_le16(cap_ShortPremble);
+ *(__le16 *)ie |= cpu_to_le16(cap_short_premble);
if (pdev_network->Privacy)
*(__le16 *)ie |= cpu_to_le16(cap_Privacy);
sz += 2;
diff --git a/drivers/staging/rtl8712/wifi.h b/drivers/staging/rtl8712/wifi.h
index 74dfc9b..2c8b729 100644
--- a/drivers/staging/rtl8712/wifi.h
+++ b/drivers/staging/rtl8712/wifi.h
@@ -441,7 +441,7 @@ static inline unsigned char *get_hdr_bssid(unsigned char *pframe)
#define cap_CFPollable BIT(2)
#define cap_CFRequest BIT(3)
#define cap_Privacy BIT(4)
-#define cap_ShortPremble BIT(5)
+#define cap_short_premble BIT(5)
/*-----------------------------------------------------------------------------
Below is the definition for 802.11i / 802.1x
--
1.9.1
next reply other threads:[~2017-05-20 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 17:56 Jaya Durga [this message]
2017-05-25 16:36 ` Greg KH
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=1495302977-26774-1-git-send-email-jayad@cdac.in \
--to=jayad@cdac.in \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®