summaryrefslogtreecommitdiff
path: root/sys/arch/powerpc
diff options
context:
space:
mode:
authorKenneth R Westerback <krw@cvs.openbsd.org>2007-09-15 14:28:18 +0000
committerKenneth R Westerback <krw@cvs.openbsd.org>2007-09-15 14:28:18 +0000
commit108d9cfcb386f7c605eb46d22d8129f639afb2bd (patch)
treece621237e28bf022b8b72fc74fc05d46688d9613 /sys/arch/powerpc
parent303c07c296b073a0e7c34ebd0cf74603baa9d96b (diff)
[fF]uther -> [fF]urther in comments and man page. First one spotted on
tech@ by Jung.
Diffstat (limited to 'sys/arch/powerpc')
-rw-r--r--sys/arch/powerpc/powerpc/pmap.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/arch/powerpc/powerpc/pmap.c b/sys/arch/powerpc/powerpc/pmap.c
index dbfd7ab5c75..d303f6cd5f1 100644
--- a/sys/arch/powerpc/powerpc/pmap.c
+++ b/sys/arch/powerpc/powerpc/pmap.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: pmap.c,v 1.101 2007/05/27 15:46:02 drahn Exp $ */
+/* $OpenBSD: pmap.c,v 1.102 2007/09/15 14:28:17 krw Exp $ */
/*
* Copyright (c) 2001, 2002, 2007 Dale Rahn.
@@ -369,7 +369,7 @@ PTED_VALID(struct pte_desc *pted)
* it is likely that it will be mapped at some point, but would it also
* make sense to use a tree/table like is use for pmap to store device
* mappings?
- * Futher notes: It seems that the PV table is only used for pmap_protect
+ * Further notes: It seems that the PV table is only used for pmap_protect
* and other paging related operations. Given this, it is not necessary
* to store any pmap_kernel() entries in PV tables and does not make
* sense to store device mappings in PV either.