mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: linux-kernel@vger.kernel.org,
	Arushi Singhal <arushisinghal19971997@gmail.com>
Subject: [PATCH 1/5] kernel: pid: remove space after open square bracket
Date: Wed, 29 Mar 2017 02:15:02 +0530	[thread overview]
Message-ID: <20170328204506.16316-2-arushisinghal19971997@gmail.com> (raw)
In-Reply-To: <20170328204506.16316-1-arushisinghal19971997@gmail.com>

Remove the space after open square bracket as reported by checkpatch.pl.

Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
---
 kernel/pid.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/pid.c b/kernel/pid.c
index 0143ac0ddceb..59ec7a671e06 100644
--- a/kernel/pid.c
+++ b/kernel/pid.c
@@ -71,7 +71,7 @@ static inline int mk_pid(struct pid_namespace *pid_ns,
 struct pid_namespace init_pid_ns = {
 	.kref = KREF_INIT(2),
 	.pidmap = {
-		[ 0 ... PIDMAP_ENTRIES-1] = { ATOMIC_INIT(BITS_PER_PAGE), NULL }
+		[0 ... PIDMAP_ENTRIES-1] = { ATOMIC_INIT(BITS_PER_PAGE), NULL }
 	},
 	.last_pid = 0,
 	.nr_hashed = PIDNS_HASH_ADDING,
-- 
2.11.0

  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 ` Arushi Singhal [this message]
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 ` [PATCH 5/5] kernel: pid_namespace.c: Do not initialise statics to 0 Arushi Singhal

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-2-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®