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 3/4] Drivers: Staging: CSR: Removed whitespace between function name and (
Date: Mon, 15 Oct 2012 00:16:52 +0900	[thread overview]
Message-ID: <1350227813-30880-3-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <1350227813-30880-1-git-send-email-antiroot@gmail.com>

Removed the unnecessary whitespace between function name and the "(",
according to the coding style.

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

diff --git a/drivers/staging/csr/data_tx.c b/drivers/staging/csr/data_tx.c
index 1bea7f0..160a6c5 100644
--- a/drivers/staging/csr/data_tx.c
+++ b/drivers/staging/csr/data_tx.c
@@ -15,7 +15,7 @@
 #include "csr_wifi_hip_unifi.h"
 #include "unifi_priv.h"
 
-int uf_verify_m4 (unifi_priv_t *priv, const unsigned char *packet,
+int uf_verify_m4(unifi_priv_t *priv, const unsigned char *packet,
 	unsigned int length) {
 	const unsigned char *p = packet;
 	u16 keyinfo;
-- 
1.7.9.5


  parent reply	other threads:[~2012-10-14 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14 15:16 [PATCH 1/4] Drivers: Staging: CSR: Fixed indentation problems on data_tx.c Sangho Yi
2012-10-14 15:16 ` [PATCH 2/4] Drivers: Staging: CSR: Removed braces for single line if statement Sangho Yi
2012-10-22 21:02   ` Greg KH
2012-10-14 15:16 ` Sangho Yi [this message]
2012-10-22 21:02   ` [PATCH 3/4] Drivers: Staging: CSR: Removed whitespace between function name and ( Greg KH
2012-10-14 15:16 ` [PATCH 4/4] Drivers: Staging: CSR: Removed whitespace before quoting newline Sangho Yi
2012-10-22 21:03   ` Greg KH
2012-10-18 13:31 ` [PATCH 1/4] Drivers: Staging: CSR: Fixed indentation problems on data_tx.c Dan Carpenter
2012-10-22 21:00 ` 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=1350227813-30880-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 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.