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 v2 3/5] include: linux: pid: Add identifier to function definition argument.
Date: Sun, 26 Mar 2017 20:21:40 +0530	[thread overview]
Message-ID: <58d7d57e.059f620a.28d36.6ef0@mx.google.com> (raw)
In-Reply-To: <cover.1490539294.git.rvarsha016@gmail.com>

Add ns as the identifier to function definition argument struct
pid_namespace and this patch fixes the checkpatch issue.

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

diff --git a/include/linux/pid.h b/include/linux/pid.h
index c27ca01..04c0a5b 100644
--- a/include/linux/pid.h
+++ b/include/linux/pid.h
@@ -131,7 +131,7 @@ extern struct pid *find_vpid(int nr);
  * Lookup a PID in the hash table, and return with it's count elevated.
  */
 extern struct pid *find_get_pid(int nr);
-extern struct pid *find_ge_pid(int nr, struct pid_namespace *);
+extern struct pid *find_ge_pid(int nr, struct pid_namespace *ns);
 int next_pidmap(struct pid_namespace *pid_ns, unsigned int last);
 
 extern struct pid *alloc_pid(struct pid_namespace *ns);
-- 
2.9.3



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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1490539294.git.rvarsha016@gmail.com>
2017-03-26 14:48 ` [PATCH v2 1/5] include: linux: pid: Update documentation Varsha Rao
2017-03-26 14:50 ` [PATCH v2 2/5] include: linux: pid: Move open brace to previous line Varsha Rao
2017-03-26 14:51 ` Varsha Rao [this message]
2017-03-26 14:53 ` [PATCH v2 4/5] include: linux: pid: Add a blank line after declarations Varsha Rao
2017-03-26 14:55 ` [PATCH v2 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=58d7d57e.059f620a.28d36.6ef0@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.