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 RESEND 00/12] Avoid CamelCases in hfa384x.h
Date: Wed, 19 Oct 2016 17:59:11 +0200	[thread overview]
Message-ID: <1476892763-21283-1-git-send-email-sergio.paracuellos@gmail.com> (raw)

This patchset fix CamelCases in hfa384x.h header file.

This file is free of CamelCases now.

This patch series are resent because an mix error in the previous sent.

Sergio Paracuellos (12):
  staging: wlan-ng: avoid CamelCase: HFA384x_RID_CNFAPBCNint
  staging: wlan-ng: avoid CamelCase: hfa384x_HostScanRequest_data
  staging: wlan-ng: avoid CamelCase: hfa384x_WPAData
  staging: wlan-ng: avoid CamelCase in fields of struct
    hfa384x_dbmcommsquality
  staging: wlan-ng: avoid CamelCase: hfa384x_CommTallies16
  staging: wlan-ng: avoid CamelCase: hfa384x_ChInfoResult
  staging: wlan-ng: avoid CamelCase: hfa384x_HScanResultSub
  staging: wlan-ng: avoid CamelCase: hfa384x_HScanResult
  staging: wlan-ng: avoid CamelCase: hfa384x_LinkStatus
  staging: wlan-ng: avoid CamelCase: hfa384x_AuthRequest
  staging: wlan-ng: avoid CamelCase: hfa384x_PSUserCount
  staging: wlan-ng: avoid CamelCase: hfa384x_KeyIDChanged

 drivers/staging/wlan-ng/hfa384x.h    | 50 ++++++++++++++++++------------------
 drivers/staging/wlan-ng/prism2mgmt.c | 12 ++++-----
 drivers/staging/wlan-ng/prism2mib.c  |  2 +-
 3 files changed, 32 insertions(+), 32 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-10-19 16:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 15:59 Sergio Paracuellos [this message]
2016-10-19 15:59 ` [PATCH RESEND 01/12] staging: wlan-ng: avoid CamelCase: HFA384x_RID_CNFAPBCNint Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 02/12] staging: wlan-ng: avoid CamelCase: hfa384x_HostScanRequest_data Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 03/12] staging: wlan-ng: avoid CamelCase: hfa384x_WPAData Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 04/12] staging: wlan-ng: avoid CamelCase in fields of struct hfa384x_dbmcommsquality Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 05/12] staging: wlan-ng: avoid CamelCase: hfa384x_CommTallies16 Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 06/12] staging: wlan-ng: avoid CamelCase: hfa384x_ChInfoResult Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 07/12] staging: wlan-ng: avoid CamelCase: hfa384x_HScanResultSub Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 08/12] staging: wlan-ng: avoid CamelCase: hfa384x_HScanResult Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 09/12] staging: wlan-ng: avoid CamelCase: hfa384x_LinkStatus Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 10/12] staging: wlan-ng: avoid CamelCase: hfa384x_AuthRequest Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 11/12] staging: wlan-ng: avoid CamelCase: hfa384x_PSUserCount Sergio Paracuellos
2016-10-19 15:59 ` [PATCH RESEND 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=1476892763-21283-1-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®