From: Sabitha George <sabitha.george@gmail.com>
To: gregkh@linuxfoundation.org, wsa+renesas@sang-engineering.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Sabitha George <sabitha.george@gmail.com>
Subject: [PATCH 1/2] staging: ks7010: Add blank line after declarations
Date: Sun, 16 Oct 2016 21:42:44 +0530 [thread overview]
Message-ID: <1476634364-26898-1-git-send-email-sabitha.george@gmail.com> (raw)
Fixes checkpatch.pl warning :Missing a blank line
after declarations
Signed-off-by: Sabitha George <sabitha.george@gmail.com>
---
drivers/staging/ks7010/ks_hostif.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/staging/ks7010/ks_hostif.c b/drivers/staging/ks7010/ks_hostif.c
index 1f9f63e..ad840f9 100644
--- a/drivers/staging/ks7010/ks_hostif.c
+++ b/drivers/staging/ks7010/ks_hostif.c
@@ -750,6 +750,7 @@ void hostif_start_confirm(struct ks_wlan_private *priv)
{
#ifdef WPS
union iwreq_data wrqu;
+
wrqu.data.length = 0;
wrqu.data.flags = 0;
wrqu.ap_addr.sa_family = ARPHRD_ETHER;
@@ -771,6 +772,7 @@ void hostif_connect_indication(struct ks_wlan_private *priv)
unsigned int old_status = priv->connect_status;
struct net_device *netdev = priv->net_dev;
union iwreq_data wrqu0;
+
connect_code = get_WORD(priv);
switch (connect_code) {
@@ -910,6 +912,7 @@ void hostif_ps_adhoc_set_confirm(struct ks_wlan_private *priv)
void hostif_infrastructure_set_confirm(struct ks_wlan_private *priv)
{
uint16_t result_code;
+
DPRINTK(3, "\n");
result_code = get_WORD(priv);
DPRINTK(3, "result code = %d\n", result_code);
@@ -975,6 +978,7 @@ void hostif_bss_scan_confirm(struct ks_wlan_private *priv)
unsigned int result_code;
struct net_device *dev = priv->net_dev;
union iwreq_data wrqu;
+
result_code = get_DWORD(priv);
DPRINTK(2, "result=%d :: scan_ind_count=%d\n", result_code,
priv->scan_ind_count);
@@ -1872,6 +1876,7 @@ void hostif_receive(struct ks_wlan_private *priv, unsigned char *p,
void hostif_sme_set_wep(struct ks_wlan_private *priv, int type)
{
uint32_t val;
+
switch (type) {
case SME_WEP_INDEX_REQUEST:
val = cpu_to_le32((uint32_t) (priv->reg.wep_index));
@@ -2335,6 +2340,7 @@ void hostif_sme_sleep_set(struct ks_wlan_private *priv)
void hostif_sme_set_key(struct ks_wlan_private *priv, int type)
{
uint32_t val;
+
switch (type) {
case SME_SET_FLAG:
val = cpu_to_le32((uint32_t) (priv->reg.privacy_invoked));
--
1.9.1
reply other threads:[~2016-10-16 16:12 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=1476634364-26898-1-git-send-email-sabitha.george@gmail.com \
--to=sabitha.george@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 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®