From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: linux-kernel@vger.kernel.org,
Arushi Singhal <arushisinghal19971997@gmail.com>
Subject: [PATCH 5/5] kernel: pid_namespace.c: Do not initialise statics to 0.
Date: Wed, 29 Mar 2017 02:15:06 +0530 [thread overview]
Message-ID: <20170328204506.16316-6-arushisinghal19971997@gmail.com> (raw)
In-Reply-To: <20170328204506.16316-1-arushisinghal19971997@gmail.com>
Do not initialise statics to 0.
static variable by default initialise to 0,so no need to explicite
initialisation.
This issue was found by checkpatch.
Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
---
kernel/pid_namespace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
index be35c2fe725f..1bfbee50177b 100644
--- a/kernel/pid_namespace.c
+++ b/kernel/pid_namespace.c
@@ -314,7 +314,7 @@ static int pid_ns_ctl_handler(struct ctl_table *table, int write,
}
extern int pid_max;
-static int zero = 0;
+static int zero;
static struct ctl_table pid_ns_ctl_table[] = {
{
.procname = "ns_last_pid",
--
2.11.0
prev parent reply other threads:[~2017-03-28 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 20:45 [PATCH 0/5] kernel: pid: Multiple checkpatch issues Arushi Singhal
2017-03-28 20:45 ` [PATCH 1/5] kernel: pid: remove space after open square bracket Arushi Singhal
2017-03-28 20:45 ` [PATCH 2/5] kernel: pid.c: Add space before the open parenthesis Arushi Singhal
2017-03-28 20:45 ` [PATCH 3/5] kernel: pid: Fix line over 80 characters Arushi Singhal
2017-03-28 20:45 ` [PATCH 4/5] kernel: pid_namespace: Remove return statement from void function Arushi Singhal
2017-03-28 20:45 ` Arushi Singhal [this message]
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=20170328204506.16316-6-arushisinghal19971997@gmail.com \
--to=arushisinghal19971997@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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®