From: Luis Henriques <henrix@sapo.pt>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
henrix@sapo.pt, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/cleanups] sched: fix typos in documentation
Date: Tue, 17 Mar 2009 11:06:25 GMT [thread overview]
Message-ID: <tip-80dd99b368cf6501be88ab517bbbb5bf352b75b8@git.kernel.org> (raw)
In-Reply-To: <20090316195809.GA6073@hades.domain.com>
Commit-ID: 80dd99b368cf6501be88ab517bbbb5bf352b75b8
Gitweb: http://git.kernel.org/tip/80dd99b368cf6501be88ab517bbbb5bf352b75b8
Author: Luis Henriques <henrix@sapo.pt>
AuthorDate: Mon, 16 Mar 2009 19:58:09 +0000
Commit: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 17 Mar 2009 12:04:40 +0100
sched: fix typos in documentation
Fixed typos in function documentation.
Signed-off-by: Luis Henriques <henrix@sapo.pt>
LKML-Reference: <20090316195809.GA6073@hades.domain.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 2f28351..489e7d9 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -2082,7 +2082,7 @@ unsigned long wait_task_inactive(struct task_struct *p, long match_state)
* it must be off the runqueue _entirely_, and not
* preempted!
*
- * So if it wa still runnable (but just not actively
+ * So if it was still runnable (but just not actively
* running right now), it's preempted, and we should
* yield - it could be a while.
*/
@@ -2574,7 +2574,7 @@ void wake_up_new_task(struct task_struct *p, unsigned long clone_flags)
#ifdef CONFIG_PREEMPT_NOTIFIERS
/**
- * preempt_notifier_register - tell me when current is being being preempted & rescheduled
+ * preempt_notifier_register - tell me when current is being preempted & rescheduled
* @notifier: notifier struct to register
*/
void preempt_notifier_register(struct preempt_notifier *notifier)
prev parent reply other threads:[~2009-03-17 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 19:58 [PATCH 1/2 -tip] sched: Fixed typos in documentation Luis Henriques
2009-03-17 11:06 ` Luis Henriques [this message]
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-80dd99b368cf6501be88ab517bbbb5bf352b75b8@git.kernel.org \
--to=henrix@sapo.pt \
--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 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.