From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: mingo@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH 5/5] Documentation, sched-arch.txt: fix the incorrect syntax
Date: Fri, 27 Dec 2013 19:41:04 +0800 [thread overview]
Message-ID: <1388144464-28458-6-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1388144464-28458-1-git-send-email-zwu.kernel@gmail.com>
From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
Documentation/scheduler/sched-arch.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/scheduler/sched-arch.txt b/Documentation/scheduler/sched-arch.txt
index 9290de7..0a7d252 100644
--- a/Documentation/scheduler/sched-arch.txt
+++ b/Documentation/scheduler/sched-arch.txt
@@ -21,7 +21,7 @@ CPU idle
========
Your cpu_idle routines need to obey the following rules:
-1. Preempt should now disabled over idle routines. Should only
+1. Preempt should be now disabled over idle routines. Should only
be enabled to call schedule() then disabled again.
2. need_resched/TIF_NEED_RESCHED is only ever set, and will never
--
1.7.6.5
prev parent reply other threads:[~2013-12-27 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 11:40 [PATCH 0/5] Sched: Some trivial typo fixes Zhi Yong Wu
2013-12-27 11:41 ` [PATCH 1/5] sched, rt: move .switched_from out of the scope of CONFIG_SMP Zhi Yong Wu
2013-12-28 9:19 ` Kirill Tkhai
2013-12-28 9:37 ` Zhi Yong Wu
2013-12-28 9:48 ` Kirill Tkhai
2013-12-28 9:59 ` Zhi Yong Wu
2013-12-27 11:41 ` [PATCH 2/5] sched, fair: fix the comment of move_tasks() Zhi Yong Wu
2013-12-27 11:41 ` [PATCH 3/5] sched, fair: fix the typo in select_idle_sibling() Zhi Yong Wu
2013-12-27 11:41 ` [PATCH 4/5] sched, fair: fix the comment of select_task_rq_fair() Zhi Yong Wu
2013-12-27 11:41 ` Zhi Yong Wu [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=1388144464-28458-6-git-send-email-zwu.kernel@gmail.com \
--to=zwu.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wuzhy@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox