From: Ben Pfaff <blp@cs.stanford.edu>
Date: Sun, 29 Jan 2006 21:55:08 +0000 (+0000)
Subject: Clarify when enable_mlfqs gets set.
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=47312fb57d6fe1d2c0377533a08f709840576873;p=pintos-anon

Clarify when enable_mlfqs gets set.
Thanks to "Yi Lang Mok" <yilangmok@stanford.edu> and others for
pointing this out.
---

diff --git a/doc/threads.texi b/doc/threads.texi
index ced5ae8..77afeda 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -511,8 +511,8 @@ must be active, but we must be able to choose the 4.4@acronym{BSD}
 scheduler
 with the @option{-mlfqs} kernel option.  Passing this
 option sets @code{enable_mlfqs}, declared in @file{threads/init.h}, to
-true, when the options are parsed by @func{parse_options}, which happens
-through midway through @func{main}.
+true when the options are parsed by @func{parse_options}, which happens
+midway through @func{main}.
 
 When the 4.4@acronym{BSD} scheduler is enabled, threads no longer
 directly control their own priorities.  The @var{priority} argument to