From: tip-bot for Rakib Mullick <rakib.mullick@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
rakib.mullick@gmail.com, a.p.zijlstra@chello.nl,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/core] sched: Remove obsolete comment from scheduler_tick()
Date: Thu, 21 Apr 2011 12:11:07 GMT [thread overview]
Message-ID: <tip-d3bf52e998056a6002b2aecfe1d25486376382ac@git.kernel.org> (raw)
In-Reply-To: <BANLkTimO4iGP0QpaHO1HHF1QOnVcQpc0cw@mail.gmail.com>
Commit-ID: d3bf52e998056a6002b2aecfe1d25486376382ac
Gitweb: http://git.kernel.org/tip/d3bf52e998056a6002b2aecfe1d25486376382ac
Author: Rakib Mullick <rakib.mullick@gmail.com>
AuthorDate: Wed, 20 Apr 2011 21:27:32 +0600
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 21 Apr 2011 11:41:36 +0200
sched: Remove obsolete comment from scheduler_tick()
scheduler_tick() is no longer called by fork code - this got discarded
a long time ago by commit bc947631d1d532 ("sched: improve efficiency
of sched_fork()").
So, remove the comment which still claims otherwise.
Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/BANLkTimO4iGP0QpaHO1HHF1QOnVcQpc0cw@mail.gmail.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 30a29ad..8cb0a57 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -4002,9 +4002,6 @@ void thread_group_times(struct task_struct *p, cputime_t *ut, cputime_t *st)
/*
* This function gets called by the timer code, with HZ frequency.
* We call it with interrupts disabled.
- *
- * It also gets called by the fork code, when changing the parent's
- * timeslices.
*/
void scheduler_tick(void)
{
parent reply other threads:[~2011-04-21 12:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BANLkTimO4iGP0QpaHO1HHF1QOnVcQpc0cw@mail.gmail.com>]
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=tip-d3bf52e998056a6002b2aecfe1d25486376382ac@git.kernel.org \
--to=rakib.mullick@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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