From: Perr Zhang <strongbox8@zoho.com>
To: mingo@redhat.com
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] sched/header: Remove a redundant comment.
Date: Fri, 2 Jun 2017 11:59:53 +0800 [thread overview]
Message-ID: <20170602035953.28949-1-strongbox8@zoho.com> (raw)
There is no more set_task_vxid() helper. remove it from the comment.
Signed-off-by: Perr Zhang <strongbox8@zoho.com>
---
include/linux/sched.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 2b69fc650201..1abaa3728bf7 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1096,8 +1096,6 @@ static inline struct pid *task_session(struct task_struct *task)
* current.
* task_xid_nr_ns() : id seen from the ns specified;
*
- * set_task_vxid() : assigns a virtual id to a task;
- *
* see also pid_nr() etc in include/linux/pid.h
*/
pid_t __task_pid_nr_ns(struct task_struct *task, enum pid_type type, struct pid_namespace *ns);
--
2.13.0
next reply other threads:[~2017-06-02 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 3:59 Perr Zhang [this message]
2017-06-05 9:13 ` [tip:sched/core] sched/header: Remove leftover, obsolete comment tip-bot for Perr Zhang
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=20170602035953.28949-1-strongbox8@zoho.com \
--to=strongbox8@zoho.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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