From: Johan Meiring <johanmeiring@gmail.com>
To: pe1dnn@amsat.org, jkosina@suse.cz, standby24x7@gmail.com,
viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Johan Meiring <johanmeiring@gmail.com>
Subject: [PATCH 3/8] staging: wlags49_h2: wl_if.h: fixes spaces-before-tabs issue
Date: Tue, 20 Nov 2012 16:44:55 +0200 [thread overview]
Message-ID: <1353422700-14485-2-git-send-email-johanmeiring@gmail.com> (raw)
In-Reply-To: <1353422700-14485-1-git-send-email-johanmeiring@gmail.com>
This commit fixes a spaces-before-tabs problem that was reported by
the checkpatch.pl tool.
Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
---
drivers/staging/wlags49_h2/wl_if.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlags49_h2/wl_if.h b/drivers/staging/wlags49_h2/wl_if.h
index 5c6b2b5..d1fdf82 100644
--- a/drivers/staging/wlags49_h2/wl_if.h
+++ b/drivers/staging/wlags49_h2/wl_if.h
@@ -75,7 +75,7 @@
#define HCF_MAX_MULTICAST 16
#define HCF_MAX_NAME_LEN 32
-#define MAX_LINE_SIZE 256
+#define MAX_LINE_SIZE 256
#define HCF_NUM_IO_PORTS 0x80
#define TX_TIMEOUT ((800 * HZ) / 1000)
--
1.7.10.4
next prev parent reply other threads:[~2012-11-20 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 14:44 [PATCH 2/8] staging: wlags49_h2: wl_if.h: fixes tab indentation Johan Meiring
2012-11-20 14:44 ` Johan Meiring [this message]
2012-11-20 14:44 ` [PATCH 4/8] staging: wlags49_h2: wl_if.h: fixes 80 char line length issues Johan Meiring
2012-11-20 14:44 ` [PATCH 5/8] staging: wlags49_h2: wl_if.h: fixes brace placement Johan Meiring
2012-11-20 14:44 ` [PATCH 6/8] staging: wlags49_h2: wl_if.h: gets rid of C99 // comments Johan Meiring
2012-11-20 14:44 ` [PATCH 7/8] staging: wlags49_h2: ap_h2.c: fixes spaces-before-tabs problems Johan Meiring
2012-11-20 14:45 ` [PATCH 8/8] staging: wlags49_h2: ap_h2.c: fixes inconsistent spacing around * Johan Meiring
2012-11-21 8:34 ` Dan Carpenter
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=1353422700-14485-2-git-send-email-johanmeiring@gmail.com \
--to=johanmeiring@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pe1dnn@amsat.org \
--cc=standby24x7@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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