summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortedu <tedu@openbsd.org>2013-06-04 22:17:34 +0000
committertedu <tedu@openbsd.org>2013-06-04 22:17:34 +0000
commite0eff259b708d215fd0c537755e77a48224070b8 (patch)
tree7c8184452a378eb107d17687e3f84d2b6abf5634
parentsentence explaining sched_lock is not a simplelock should be a sentence. (diff)
downloadwireguard-openbsd-e0eff259b708d215fd0c537755e77a48224070b8.tar.xz
wireguard-openbsd-e0eff259b708d215fd0c537755e77a48224070b8.zip
even better now text now.
-rw-r--r--sys/sys/sched.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/sys/sys/sched.h b/sys/sys/sched.h
index 0223bb9b50c..c514cffc1f6 100644
--- a/sys/sys/sched.h
+++ b/sys/sys/sched.h
@@ -1,4 +1,4 @@
-/* $OpenBSD: sched.h,v 1.32 2013/06/04 22:16:23 tedu Exp $ */
+/* $OpenBSD: sched.h,v 1.33 2013/06/04 22:17:34 tedu Exp $ */
/* $NetBSD: sched.h,v 1.2 1999/02/28 18:14:58 ross Exp $ */
/*-
@@ -180,8 +180,8 @@ void remrunqueue(struct proc *);
/*
* XXX Instead of using struct lock for the kernel lock and thus requiring us
* XXX to implement simplelocks, causing all sorts of fine-grained locks all
- * XXX over our tree getting activated, the sched_lock is a different kind of
- * XXX lock toi avoid introducing locking protocol bugs.
+ * XXX over our tree to be activated, the sched_lock is a different kind of
+ * XXX lock to avoid introducing locking protocol bugs.
*/
extern struct __mp_lock sched_lock;