From: Juliana Rodrigues <juliana.orod@gmail.com>
To: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: [PATCH v2 09/13] staging: wlan-ng: renames hfa384x_AssocStatus to avoid camelcase
Date: Sat, 8 Oct 2016 06:48:46 -0300 [thread overview]
Message-ID: <20161008094846.GA13717@spock> (raw)
In-Reply-To: <cover.1475919731.git.juliana.orod@gmail.com>
Renames the camelcased struct hfa384x_AssocStatus to hfa384x_assoc_status
in order to fix a checkpatch warning.
Signed-off-by: Juliana Rodrigues <juliana.orod@gmail.com>
---
drivers/staging/wlan-ng/hfa384x.h | 4 ++--
drivers/staging/wlan-ng/prism2sta.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlan-ng/hfa384x.h b/drivers/staging/wlan-ng/hfa384x.h
index 7b6b373..adbac69b 100644
--- a/drivers/staging/wlan-ng/hfa384x.h
+++ b/drivers/staging/wlan-ng/hfa384x.h
@@ -733,7 +733,7 @@ struct hfa384x_LinkStatus {
#define HFA384x_ASSOCSTATUS_REASSOC ((u16)2)
#define HFA384x_ASSOCSTATUS_AUTHFAIL ((u16)5)
-struct hfa384x_AssocStatus {
+struct hfa384x_assoc_status {
u16 assocstatus;
u8 sta_addr[ETH_ALEN];
/* old_ap_addr is only valid if assocstatus == 2 */
@@ -768,7 +768,7 @@ union hfa384x_infodata {
struct hfa384x_ChInfoResult chinforesult;
struct hfa384x_HScanResult hscanresult;
struct hfa384x_LinkStatus linkstatus;
- struct hfa384x_AssocStatus assocstatus;
+ struct hfa384x_assoc_status assocstatus;
struct hfa384x_AuthRequest authreq;
struct hfa384x_PSUserCount psusercnt;
struct hfa384x_KeyIDChanged keyidchanged;
diff --git a/drivers/staging/wlan-ng/prism2sta.c b/drivers/staging/wlan-ng/prism2sta.c
index 0d2bc69..b39ef74 100644
--- a/drivers/staging/wlan-ng/prism2sta.c
+++ b/drivers/staging/wlan-ng/prism2sta.c
@@ -1474,7 +1474,7 @@ static void prism2sta_inf_assocstatus(struct wlandevice *wlandev,
struct hfa384x_inf_frame *inf)
{
struct hfa384x *hw = wlandev->priv;
- struct hfa384x_AssocStatus rec;
+ struct hfa384x_assoc_status rec;
int i;
memcpy(&rec, &inf->info.assocstatus, sizeof(rec));
--
2.10.0
next prev parent reply other threads:[~2016-10-08 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1475919731.git.juliana.orod@gmail.com>
2016-10-08 9:46 ` [PATCH v2 01/13] staging: wlan-ng: aligned block to open parenthesis Juliana Rodrigues
2016-10-08 9:46 ` [PATCH v2 02/13] staging: wlan-ng: fixed lines over 80 characters Juliana Rodrigues
2016-10-08 9:47 ` [PATCH v2 03/13] staging: wlan-ng: renames hfa384x_InfFrame to avoid camelcase Juliana Rodrigues
2016-10-08 9:47 ` [PATCH v2 04/13] staging: wlan-ng: renames hfa384x_CommTallies32 " Juliana Rodrigues
2016-10-08 9:47 ` [PATCH v2 05/13] staging: wlan-ng: renames hfa384x_ScanResult " Juliana Rodrigues
2016-10-08 9:47 ` [PATCH v2 06/13] staging: wlan-ng: renames hfa384x_JoinRequest_data " Juliana Rodrigues
2016-10-08 9:48 ` [PATCH v2 07/13] staging: wlan-ng: renames hfa384x_scanResultSub " Juliana Rodrigues
2016-10-08 9:48 ` [PATCH v2 08/13] staging: wlan-ng: renames hfa384x_ChInfoResultSub " Juliana Rodrigues
2016-10-08 9:48 ` Juliana Rodrigues [this message]
2016-10-08 9:49 ` [PATCH v2 10/13] staging: wlan-ng: renames hfa384x_authenticateStation_data " Juliana Rodrigues
2016-10-08 9:49 ` [PATCH v2 11/13] staging: wlan-ng: renames CQ_currBSS " Juliana Rodrigues
2016-10-08 9:49 ` [PATCH v2 12/13] staging: wlan-ng: renames ASL_currBSS " Juliana Rodrigues
2016-10-08 9:49 ` [PATCH v2 13/13] staging: wlan-ng: renames ANL_currFC " Juliana Rodrigues
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=20161008094846.GA13717@spock \
--to=juliana.orod@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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 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.