All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/4] staging: csr: Fixed foo ++; to foo++; on mlme.c
Date: Wed, 17 Oct 2012 01:36:48 +0900	[thread overview]
Message-ID: <1350405408-2702-4-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <1350405408-2702-1-git-send-email-antiroot@gmail.com>

Writing code as foo ++; is a coding style ERROR, so I modifed the code
to foo++;.

Signed-off-by: Sangho Yi <antiroot@gmail.com>
---
 drivers/staging/csr/mlme.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/csr/mlme.c b/drivers/staging/csr/mlme.c
index e4ecdd8..25b2d1d 100644
--- a/drivers/staging/csr/mlme.c
+++ b/drivers/staging/csr/mlme.c
@@ -118,7 +118,7 @@ unifi_mlme_wait_for_reply(unifi_priv_t *priv, ul_client_t *pcli,
 			/* Wait for the next signal. */
 			pcli->wake_up_wq_id = 0;
 
-			retries ++;
+			retries++;
 			if (retries >= 3) {
 				unifi_error(priv, "mlme_wait: confirm wait retries exhausted (0x%.4X - exp 0x%.4X)\n",
 					pcli->wake_up_wq_id, sig_reply_id);
-- 
1.7.9.5


  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 ` [PATCH 3/4] staging: csr: removed single line { } braces from for and if statements Sangho Yi
2012-10-16 16:36 ` Sangho Yi [this message]
2012-10-22 21:05 ` [PATCH 1/4] staging: csr: Fixed indentation from 4 spaces to tabs on mlme.c 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-4-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 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.