From: Juliana Rodrigues <juliana.orod@gmail.com>
To: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: [PATCH v2 00/13] wlan-ng prism2sta cleanup
Date: Sat, 8 Oct 2016 06:45:51 -0300 [thread overview]
Message-ID: <20161008094551.GA12055@spock> (raw)
This patchset focuses on solving the following checkpatch warnings
found on wlan-ng, mostly related to prism2sta file:
- Lines over 80 characters
- Block alignment to parenthesis
- Camelcased variables and structs
Changes in v2:
- fixed alignment blocks
- changed pointer line break for better comprehension
Juliana Rodrigues (13):
staging: wlan-ng: aligned block to open parenthesis
staging: wlan-ng: fixed lines over 80 characters
staging: wlan-ng: renames hfa384x_InfFrame to avoid camelcase
staging: wlan-ng: renames hfa384x_CommTallies32 to avoid camelcase
staging: wlan-ng: renames hfa384x_ScanResult to avoid camelcase
staging: wlan-ng: renames hfa384x_JoinRequest_data to avoid camelcase
staging: wlan-ng: renames hfa384x_scanResultSub to avoid camelcase
staging: wlan-ng: renames hfa384x_ChInfoResultSub to avoid camelcase
staging: wlan-ng: renames hfa384x_AssocStatus to avoid camelcase
staging: wlan-ng: renames hfa384x_authenticateStation_data to avoid
camelcase
staging: wlan-ng: renames CQ_currBSS to avoid camelcase
staging: wlan-ng: renames ASL_currBSS to avoid camelcase
staging: wlan-ng: renames ANL_currFC to avoid camelcase
drivers/staging/wlan-ng/hfa384x.h | 42 ++++-----
drivers/staging/wlan-ng/prism2mgmt.h | 3 +-
drivers/staging/wlan-ng/prism2sta.c | 167 ++++++++++++++++++-----------------
3 files changed, 109 insertions(+), 103 deletions(-)
--
2.10.0
reply other threads:[~2016-10-08 9:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161008094551.GA12055@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.