mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 08/12] staging: wlan-ng: avoid CamelCase: hfa384x_HScanResult
Date: Wed, 19 Oct 2016 17:52:43 +0200	[thread overview]
Message-ID: <1476892367-21061-14-git-send-email-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <1476892367-21061-1-git-send-email-sergio.paracuellos@gmail.com>

Replace CamelCase struct name with underscores to comply 
with the standard kernel coding style.

Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
 drivers/staging/wlan-ng/hfa384x.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/wlan-ng/hfa384x.h b/drivers/staging/wlan-ng/hfa384x.h
index 46855fe..e5b72dc 100644
--- a/drivers/staging/wlan-ng/hfa384x.h
+++ b/drivers/staging/wlan-ng/hfa384x.h
@@ -707,7 +707,7 @@ struct hfa384x_hscan_result_sub {
 	u16 atim;
 } __packed;
 
-struct hfa384x_HScanResult {
+struct hfa384x_hscan_result {
 	u16 nresult;
 	u16 rsvd;
 	struct hfa384x_hscan_result_sub result[HFA384x_HSCANRESULT_MAX];
@@ -766,7 +766,7 @@ struct hfa384x_KeyIDChanged {
 	struct hfa384x_comm_tallies_32 commtallies32;
 	struct hfa384x_scan_result scanresult;
 	struct hfa384x_ch_info_result chinforesult;
-	struct hfa384x_HScanResult hscanresult;
+	struct hfa384x_hscan_result hscanresult;
 	struct hfa384x_LinkStatus linkstatus;
 	struct hfa384x_assoc_status assocstatus;
 	struct hfa384x_AuthRequest authreq;
-- 
1.9.1

  parent reply	other threads:[~2016-10-19 15:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 15:52 [PATCH 00/12] Avoid CamelCases in hfa384x.h Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 01/12] staging: wlan-ng: avoid CamelCase: HFA384x_RID_CNFAPBCNint Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 1/5] staging: wlan-ng: Replace data type declaration with variable of same type in cfg80211.c Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 02/12] staging: wlan-ng: avoid CamelCase: hfa384x_HostScanRequest_data Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 2/5] staging: wlan-ng: Replace data type declaration with variable of same type in hfa384x_usb.c Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 03/12] staging: wlan-ng: avoid CamelCase: hfa384x_WPAData Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 3/5] staging: wlan-ng: Replace data type declaration with variable of same type in p80211conv.c Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 04/12] staging: wlan-ng: avoid CamelCase in fields of struct hfa384x_dbmcommsquality Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 4/5] staging: wlan-ng: Replace data type declaration with variable of same type in p80211netdev.c Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 05/12] staging: wlan-ng: avoid CamelCase: hfa384x_CommTallies16 Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 5/5] staging: wlan-ng: Replace data type declaration with variable of same type in prism2sta.c Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 06/12] staging: wlan-ng: avoid CamelCase: hfa384x_ChInfoResult Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 07/12] staging: wlan-ng: avoid CamelCase: hfa384x_HScanResultSub Sergio Paracuellos
2016-10-19 15:52 ` Sergio Paracuellos [this message]
2016-10-19 15:52 ` [PATCH 09/12] staging: wlan-ng: avoid CamelCase: hfa384x_LinkStatus Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 10/12] staging: wlan-ng: avoid CamelCase: hfa384x_AuthRequest Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 11/12] staging: wlan-ng: avoid CamelCase: hfa384x_PSUserCount Sergio Paracuellos
2016-10-19 15:52 ` [PATCH 12/12] staging: wlan-ng: avoid CamelCase: hfa384x_KeyIDChanged Sergio Paracuellos

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=1476892367-21061-14-git-send-email-sergio.paracuellos@gmail.com \
    --to=sergio.paracuellos@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --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®