From: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
To: <linux-kernel@vger.kernel.org>, <linux-parport@lists.infradead.org>
Cc: <sudipm.mukherjee@gmail.com>, <sudip.mukherjee@codethink.co.uk>,
<akpm@linux-foundation.org>,
Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Subject: [PATCH 3/5] parport: cleanup statics initialization to NULL or 0
Date: Mon, 17 Jul 2017 17:37:00 +0100 [thread overview]
Message-ID: <20170717163702.17427-4-palminha@synopsys.com> (raw)
In-Reply-To: <20170717163702.17427-1-palminha@synopsys.com>
based on checkpatch, cleanup the "do not initialise statics to" 0 or NULL.
Signed-off-by: Carlos Palminha <palminha@synopsys.com>
---
drivers/parport/daisy.c | 2 +-
drivers/parport/parport_atari.c | 2 +-
drivers/parport/parport_ip32.c | 2 +-
drivers/parport/parport_mfc3.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/parport/daisy.c b/drivers/parport/daisy.c
index 209f3e61964e..568d3733ae4e 100644
--- a/drivers/parport/daisy.c
+++ b/drivers/parport/daisy.c
@@ -44,7 +44,7 @@ static struct daisydev {
} *topology = NULL;
static DEFINE_SPINLOCK(topology_lock);
-static int numdevs = 0;
+static int numdevs;
/* Forward-declaration of lower-level functions. */
static int mux_present(struct parport *port);
diff --git a/drivers/parport/parport_atari.c b/drivers/parport/parport_atari.c
index b8da1b5f550c..8303cc373ab0 100644
--- a/drivers/parport/parport_atari.c
+++ b/drivers/parport/parport_atari.c
@@ -18,7 +18,7 @@
#include <asm/irq.h>
#include <asm/atariints.h>
-static struct parport *this_port = NULL;
+static struct parport *this_port;
static unsigned char
parport_atari_read_data(struct parport *p)
diff --git a/drivers/parport/parport_ip32.c b/drivers/parport/parport_ip32.c
index dcbeeb220dda..0186db7680d4 100644
--- a/drivers/parport/parport_ip32.c
+++ b/drivers/parport/parport_ip32.c
@@ -138,7 +138,7 @@ static unsigned int features = ~0U;
static bool verbose_probing = DEFAULT_VERBOSE_PROBING;
/* We do not support more than one port. */
-static struct parport *this_port = NULL;
+static struct parport *this_port;
/* Timing constants for FIFO modes. */
#define FIFO_NFAULT_TIMEOUT 100 /* milliseconds */
diff --git a/drivers/parport/parport_mfc3.c b/drivers/parport/parport_mfc3.c
index d650b00ce38a..2467633504b6 100644
--- a/drivers/parport/parport_mfc3.c
+++ b/drivers/parport/parport_mfc3.c
@@ -174,7 +174,7 @@ DPRINTK(KERN_DEBUG "read_status %02x\n", status);
return status;
}
-static int use_cnt = 0;
+static int use_cnt;
static irqreturn_t mfc3_interrupt(int irq, void *dev_id)
{
--
2.11.0
next prev parent reply other threads:[~2017-07-17 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 16:36 [PATCH 0/5] parport: cleanup several checkpatch issues Carlos Palminha
2017-07-17 16:36 ` [PATCH 1/5] parport: add newline to trailing statements Carlos Palminha
2017-08-07 20:42 ` Sudip Mukherjee
2017-07-17 16:36 ` [PATCH 2/5] parport: cleanup prohibited space after functions name Carlos Palminha
2017-08-07 20:49 ` Sudip Mukherjee
2017-07-17 16:37 ` Carlos Palminha [this message]
2017-07-17 16:37 ` [PATCH 4/5] parport: move open braces to the same line Carlos Palminha
2017-07-17 16:40 ` [PATCH 5/5] parport: remove unnecessary braces Carlos Palminha
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=20170717163702.17427-4-palminha@synopsys.com \
--to=carlos.palminha@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=sudip.mukherjee@codethink.co.uk \
--cc=sudipm.mukherjee@gmail.com \
/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®