From: Scott Matheina <scott@matheina.com>
To: linux-kernel@vger.kernel.org
Cc: Aditya Shankar <aditya.shankar@microchip.com>,
Ganesh Krishna <ganesh.krishna@microchip.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org
Subject: [PATCH 2/7] staging:wilc1000:host_interface.c Added braces {} on else statemement
Date: Wed, 11 Jan 2017 21:38:33 -0600 [thread overview]
Message-ID: <1484192328-16825-2-git-send-email-scott@matheina.com> (raw)
In-Reply-To: <1484192328-16825-1-git-send-email-scott@matheina.com>
Fixes checkpatch warning: braces {} should be used on all arms of
this statement
Signed-off-by: Scott Matheina <scott@matheina.com>
---
drivers/staging/wilc1000/host_interface.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
index b00ea75..c307cce 100644
--- a/drivers/staging/wilc1000/host_interface.c
+++ b/drivers/staging/wilc1000/host_interface.c
@@ -3998,8 +3998,9 @@ static void *host_int_ParseJoinBssParam(struct network_info *ptstrNetworkInfo)
pNewJoinBssParam->rsn_found = true;
index += pu8IEs[index + 1] + 2;
continue;
- } else
+ } else {
index += pu8IEs[index + 1] + 2;
+ }
}
}
--
2.7.4
next parent reply other threads:[~2017-01-12 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1484192328-16825-1-git-send-email-scott@matheina.com>
2017-01-12 3:38 ` Scott Matheina [this message]
2017-01-12 3:38 ` [PATCH 3/7] staging:wilc1000:linux_wlan.c Align code to match open parenthesis Scott Matheina
2017-01-12 3:38 ` [PATCH 4/7] staging:wilc1000:wilc_debugfs.c Aligns " Scott Matheina
2017-01-12 3:38 ` [PATCH 5/7] staging:wilc1000:wilc_debugfs.c Removes multiple blank lines Scott Matheina
2017-01-12 3:38 ` [PATCH 6/7] staging:wilc1000:wilc_sdio.c Aligns code match open parenthesis Scott Matheina
2017-01-12 3:38 ` [PATCH 7/7] staging:wilc1000:wilc_sdio.c Deleted un-needed blank lines Scott Matheina
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=1484192328-16825-2-git-send-email-scott@matheina.com \
--to=scott@matheina.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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