All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gargi Sharma <gs051095@gmail.com>
To: mawilcox@microsoft.com
Cc: outreachy-kernel@googlegroups.com, Gargi Sharma <gs051095@gmail.com>
Subject: [PATCH 2/3] kernel: pid_namespace: Fix line over 80 characters
Date: Sun, 26 Mar 2017 20:18:14 +0530	[thread overview]
Message-ID: <38ecc07b35b00ee00b4c90f11e1dd17bffe26d36.1490539466.git.gs051095@gmail.com> (raw)
In-Reply-To: <cover.1490539466.git.gs051095@gmail.com>
In-Reply-To: <cover.1490539466.git.gs051095@gmail.com>

Line over 80 characters are split to fix the following checkpatch
issue:
WARNING: line over 80 characters

Signed-off-by: Gargi Sharma <gs051095@gmail.com>
---
 kernel/pid_namespace.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
index 6ace1e3..18f5385 100644
--- a/kernel/pid_namespace.c
+++ b/kernel/pid_namespace.c
@@ -92,8 +92,9 @@ static void dec_pid_namespaces(struct ucounts *ucounts)
 	dec_ucount(ucounts, UCOUNT_PID_NAMESPACES);
 }
 
-static struct pid_namespace *create_pid_namespace(struct user_namespace *user_ns,
-	struct pid_namespace *parent_pid_ns)
+static struct
+pid_namespace *create_pid_namespace(struct user_namespace *user_ns,
+				    struct pid_namespace *parent_pid_ns)
 {
 	struct pid_namespace *ns;
 	unsigned int level = parent_pid_ns->level + 1;
-- 
2.7.4



  parent reply	other threads:[~2017-03-26 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 14:48 [PATCH 0/3] Fix multiple checkpatch issues Gargi Sharma
2017-03-26 14:48 ` [PATCH 1/3] kernel: pid_namespace: Remove return statement from void function Gargi Sharma
2017-03-27 15:50   ` Matthew Wilcox
2017-03-26 14:48 ` Gargi Sharma [this message]
2017-03-27 15:51   ` [PATCH 2/3] kernel: pid_namespace: Fix line over 80 characters Matthew Wilcox
2017-03-27 19:12   ` Arushi Singhal
2017-03-27 19:15     ` Arushi Singhal
2017-03-26 14:48 ` [PATCH 3/3] kernel: pid_namespace: Do not initialise statics to 0 Gargi Sharma

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=38ecc07b35b00ee00b4c90f11e1dd17bffe26d36.1490539466.git.gs051095@gmail.com \
    --to=gs051095@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.