All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varsha Rao <rvarsha016@gmail.com>
To: mawilcox@microsoft.com
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: [PATCH 4/5] include: linux: pid: Add a blank line after declarations.
Date: Sun, 26 Mar 2017 15:37:53 +0530	[thread overview]
Message-ID: <58d792fb.09b8620a.585f4.540f@mx.google.com> (raw)
In-Reply-To: <cover.1490516333.git.rvarsha016@gmail.com>

Add a blank line after declarations and this patch fixes the checkpatch
issue.

Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
---
 include/linux/pid.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/pid.h b/include/linux/pid.h
index b450100..1de53e8 100644
--- a/include/linux/pid.h
+++ b/include/linux/pid.h
@@ -152,6 +152,7 @@ extern void disable_pid_allocation(struct pid_namespace *ns);
 static inline struct pid_namespace *ns_of_pid(struct pid *pid)
 {
 	struct pid_namespace *ns = NULL;
+
 	if (pid)
 		ns = pid->numbers[pid->level].ns;
 	return ns;
@@ -182,6 +183,7 @@ static inline bool is_child_reaper(struct pid *pid)
 static inline pid_t pid_nr(struct pid *pid)
 {
 	pid_t nr = 0;
+
 	if (pid)
 		nr = pid->numbers[0].nr;
 	return nr;
-- 
2.9.3



  parent reply	other threads:[~2017-03-26 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1490516333.git.rvarsha016@gmail.com>
2017-03-26 10:04 ` [PATCH 1/5] include: linux: pid: Update documentation Varsha Rao
2017-03-26 10:49   ` [Outreachy kernel] " Julia Lawall
2017-03-26 13:52     ` Matthew Wilcox
2017-03-26 14:10       ` Varsha Rao
2017-03-26 10:05 ` [PATCH 2/5] include: linux: pid: Move open brace to previous line Varsha Rao
2017-03-26 10:06 ` [PATCH 3/5] include: linux: pid: Add identifier to function definition argument Varsha Rao
2017-03-26 10:07 ` Varsha Rao [this message]
2017-03-26 10:08 ` [PATCH 5/5] include: linux: pid: Remove space before tabs Varsha Rao

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=58d792fb.09b8620a.585f4.540f@mx.google.com \
    --to=rvarsha016@gmail.com \
    --cc=mawilcox@microsoft.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.