[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor/release-0.3.2] Fix a wide comment
commit 9fbc835f10e9fba6a9b0c6643a41aee9c8aa05c2
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Fri Nov 17 09:57:15 2017 -0500
Fix a wide comment
---
src/or/scheduler.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/or/scheduler.c b/src/or/scheduler.c
index dabac386d..cbf51447b 100644
--- a/src/or/scheduler.c
+++ b/src/or/scheduler.c
@@ -258,9 +258,10 @@ select_scheduler(void)
/* We should only log this once in most cases. If it was the kernel
* losing support for kist that caused scheduler_can_use_kist() to
* return false, then this flag makes sure we only log this message
- * once. If it was the consensus that switched from "yes use kist" to
- * "no don't use kist", then we still set the flag so we log once, but
- * we unset the flag elsewhere if we ever can_use_kist() again.
+ * once. If it was the consensus that switched from "yes use kist"
+ * to "no don't use kist", then we still set the flag so we log
+ * once, but we unset the flag elsewhere if we ever can_use_kist()
+ * again.
*/
have_logged_kist_suddenly_disabled = 1;
log_notice(LD_SCHED, "Scheduler type KIST has been disabled by "
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits