From: Shailendra Verma <shailendra.capricorn@gmail.com>
To: Tim Waugh <tim@cyberelk.net>
Cc: linux-kernel@vger.kernel.org,
Shailendra Verma <shailendra.capricorn@gmail.com>
Subject: [PATCH] block:paride - Do not initialise statics to 0.
Date: Tue, 26 May 2015 02:04:47 +0530 [thread overview]
Message-ID: <1432586087-5711-1-git-send-email-shailendra.capricorn@gmail.com> (raw)
Static variables are initialised to 0 by GCC.
Fixes the following checkpatch errors:
ERROR: do not initialise statics to 0 or NULL
FILE: drivers/block/paride/pd.c:129:
static bool verbose = 0;
FILE: drivers/block/paride/pf.c:129:
static bool verbose = 0;
FILE: drivers/block/paride/pt.c:120:
static bool verbose = 0;
Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
---
drivers/block/paride/pd.c | 2 +-
drivers/block/paride/pf.c | 2 +-
drivers/block/paride/pt.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/block/paride/pd.c b/drivers/block/paride/pd.c
index d48715b..f7a142a 100644
--- a/drivers/block/paride/pd.c
+++ b/drivers/block/paride/pd.c
@@ -126,7 +126,7 @@
*/
#include <linux/types.h>
-static bool verbose = 0;
+static bool verbose;
static int major = PD_MAJOR;
static char *name = PD_NAME;
static int cluster = 64;
diff --git a/drivers/block/paride/pf.c b/drivers/block/paride/pf.c
index 9a15fd3..8bfbb13 100644
--- a/drivers/block/paride/pf.c
+++ b/drivers/block/paride/pf.c
@@ -126,7 +126,7 @@
*/
-static bool verbose = 0;
+static bool verbose;
static int major = PF_MAJOR;
static char *name = PF_NAME;
static int cluster = 64;
diff --git a/drivers/block/paride/pt.c b/drivers/block/paride/pt.c
index 2596042..3679582c 100644
--- a/drivers/block/paride/pt.c
+++ b/drivers/block/paride/pt.c
@@ -117,7 +117,7 @@
*/
-static bool verbose = 0;
+static bool verbose;
static int major = PT_MAJOR;
static char *name = PT_NAME;
static int disable = 0;
--
1.7.9.5
reply other threads:[~2015-05-25 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1432586087-5711-1-git-send-email-shailendra.capricorn@gmail.com \
--to=shailendra.capricorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cyberelk.net \
/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
all inboxes | Powered by JetHome®