From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: linux-kernel@vger.kernel.org,
Arushi Singhal <arushisinghal19971997@gmail.com>
Subject: [PATCH 3/5] kernel: pid: Fix line over 80 characters
Date: Wed, 29 Mar 2017 02:15:04 +0530 [thread overview]
Message-ID: <20170328204506.16316-4-arushisinghal19971997@gmail.com> (raw)
In-Reply-To: <20170328204506.16316-1-arushisinghal19971997@gmail.com>
This patch splits line over 80 characters addressing checkpatch.pl
warning
Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
---
kernel/pid.c | 4 +++-
kernel/pid_namespace.c | 7 +++++--
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/kernel/pid.c b/kernel/pid.c
index 5822142ca92a..dd514309d982 100644
--- a/kernel/pid.c
+++ b/kernel/pid.c
@@ -439,7 +439,9 @@ struct task_struct *pid_task(struct pid *pid, enum pid_type type)
first = rcu_dereference_check(hlist_first_rcu(&pid->tasks[type]),
lockdep_tasklist_lock_is_held());
if (first)
- result = hlist_entry(first, struct task_struct, pids[(type)].node);
+ result = hlist_entry(first,
+ struct task_struct,
+ pids[(type)].node);
}
return result;
}
diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
index de461aa0bf9a..778959ecd5c3 100644
--- a/kernel/pid_namespace.c
+++ b/kernel/pid_namespace.c
@@ -75,7 +75,9 @@ static struct kmem_cache *create_pid_cachep(int nr_ids)
static void proc_cleanup_work(struct work_struct *work)
{
- struct pid_namespace *ns = container_of(work, struct pid_namespace, proc_work);
+ struct pid_namespace *ns = container_of(work,
+ struct pid_namespace,
+ proc_work);
pid_ns_release_proc(ns);
}
@@ -89,7 +91,8 @@ static struct ucounts *inc_pid_namespaces(struct user_namespace *ns)
static void dec_pid_namespaces(struct ucounts *ucounts)
{
- dec_ucount(ucounts, UCOUNT_PID_NAMESPACES);
+ dec_ucount(ucounts,
+ UCOUNT_PID_NAMESPACES);
}
static struct pid_namespace *create_pid_namespace(struct user_namespace *user_ns,
--
2.11.0
next prev parent reply other threads:[~2017-03-28 20:47 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 ` Arushi Singhal [this message]
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-4-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®