From: Sangho Yi <antiroot@gmail.com>
To: devel@driverdev.osuosl.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Sangho Yi <antiroot@gmail.com>
Subject: [PATCH 3/4] staging: csr: removed single line { } braces from for and if statements.
Date: Wed, 17 Oct 2012 01:36:47 +0900 [thread overview]
Message-ID: <1350405408-2702-3-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <1350405408-2702-1-git-send-email-antiroot@gmail.com>
Yes, just removed the single line covering braces from the for() and
if(), and the corresponding else statements on mlme.c.
Signed-off-by: Sangho Yi <antiroot@gmail.com>
---
drivers/staging/csr/mlme.c | 20 +++++++-------------
1 file changed, 7 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/csr/mlme.c b/drivers/staging/csr/mlme.c
index dba12b2..e4ecdd8 100644
--- a/drivers/staging/csr/mlme.c
+++ b/drivers/staging/csr/mlme.c
@@ -89,11 +89,10 @@ unifi_mlme_wait_for_reply(unifi_priv_t *priv, ul_client_t *pcli,
} else {
/* Get the sequence number of the signal
* that we previously set. */
- if (pcli->seq_no != 0) {
+ if (pcli->seq_no != 0)
sent_seq_no = pcli->seq_no - 1;
- } else {
+ else
sent_seq_no = 0x0F;
- }
unifi_trace(priv, UDBG5,
"Received 0x%.4X, seq: (r:%d, s:%d)\n",
@@ -193,9 +192,8 @@ unifi_mlme_blocking_request(unifi_priv_t *priv, ul_client_t *pcli,
* if the signal has been successfully set.
*/
pcli->seq_no++;
- if (pcli->seq_no > 0x0F) {
+ if (pcli->seq_no > 0x0F)
pcli->seq_no = 0;
- }
r = unifi_mlme_wait_for_reply(priv, pcli,
(sig->SignalPrimitiveHeader.SignalId + 1), timeout);
@@ -287,14 +285,12 @@ uf_abort_mlme(unifi_priv_t *priv)
priv->io_aborted = 1;
ul_cli = priv->netdev_client;
- if (ul_cli) {
+ if (ul_cli)
wake_up_interruptible(&ul_cli->udi_wq);
- }
ul_cli = priv->wext_client;
- if (ul_cli) {
+ if (ul_cli)
wake_up_interruptible(&ul_cli->udi_wq);
- }
return 0;
} /* uf_abort_mlme() */
@@ -391,11 +387,9 @@ static const struct mlme_code Reason_codes[] = {
static const char *
lookup_something(const struct mlme_code *n, int id)
{
- for (; n->name; n++) {
- if (n->id == id) {
+ for (; n->name; n++)
+ if (n->id == id)
return n->name;
- }
- }
/* not found */
return NULL;
--
1.7.9.5
next prev parent reply other threads:[~2012-10-16 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 16:36 [PATCH 1/4] staging: csr: Fixed indentation from 4 spaces to tabs on mlme.c Sangho Yi
2012-10-16 16:36 ` [PATCH 2/4] staging: csr: Fixed exceeding 80 chars per line " Sangho Yi
2012-10-16 16:36 ` Sangho Yi [this message]
2012-10-16 16:36 ` [PATCH 4/4] staging: csr: Fixed foo ++; to foo++; " Sangho Yi
2012-10-22 21:05 ` [PATCH 1/4] staging: csr: Fixed indentation from 4 spaces to tabs " Greg KH
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=1350405408-2702-3-git-send-email-antiroot@gmail.com \
--to=antiroot@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
Powered by JetHome