From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: outreachy-kernel@googlegroups.com
Subject: [PATCH] kernel: pid_namespace.c: Remove spaces before tabs
Date: Sun, 26 Mar 2017 23:56:33 +0530 [thread overview]
Message-ID: <20170326182633.GA7742@arushi-HP-Pavilion-Notebook> (raw)
This patch is to remove unneeded spaces before tabs so as to
follow kernel coding conventions.
Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
---
kernel/pid_namespace.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
index 850a87a1de2a..8ea1dc6ed25b 100644
--- a/kernel/pid_namespace.c
+++ b/kernel/pid_namespace.c
@@ -229,11 +229,11 @@ void zap_pid_ns_processes(struct pid_namespace *pid_ns)
* to exit.
*
* Note: This signals each threads in the namespace - even those that
- * belong to the same thread group, To avoid this, we would have
- * to walk the entire tasklist looking a processes in this
- * namespace, but that could be unnecessarily expensive if the
- * pid namespace has just a few processes. Or we need to
- * maintain a tasklist for each pid namespace.
+ * belong to the same thread group, To avoid this, we would have
+ * to walk the entire tasklist looking a processes in this
+ * namespace, but that could be unnecessarily expensive if the
+ * pid namespace has just a few processes. Or we need to
+ * maintain a tasklist for each pid namespace.
*
*/
read_lock(&tasklist_lock);
--
2.11.0
reply other threads:[~2017-03-26 18:28 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=20170326182633.GA7742@arushi-HP-Pavilion-Notebook \
--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