diff options
Diffstat (limited to 'sys/kern/vfs_init.c')
| -rw-r--r-- | sys/kern/vfs_init.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/sys/kern/vfs_init.c b/sys/kern/vfs_init.c index 4478dce690c..523aa8d4a55 100644 --- a/sys/kern/vfs_init.c +++ b/sys/kern/vfs_init.c @@ -1,4 +1,4 @@ -/* $OpenBSD: vfs_init.c,v 1.24 2009/01/14 21:24:08 fgsch Exp $ */ +/* $OpenBSD: vfs_init.c,v 1.25 2010/01/14 23:12:11 schwarze Exp $ */ /* $NetBSD: vfs_init.c,v 1.6 1996/02/09 19:00:58 christos Exp $ */ /* @@ -76,12 +76,12 @@ typedef int (*PFI)(void *); * An undocumented feature of this approach to defining operations is that * there can be multiple entries in vfs_opv_descs for the same operations * vector. This allows third parties to extend the set of operations - * supported by another layer in a binary compatibile way. For example, + * supported by another layer in a binary compatible way. For example, * assume that NFS needed to be modified to support Ficus. NFS has an entry * (probably nfs_vnopdeop_decls) declaring all the operations NFS supports by * default. Ficus could add another entry (ficus_nfs_vnodeop_decl_entensions) * listing those new operations Ficus adds to NFS, all without modifying the - * NFS code. (Of couse, the OTW NFS protocol still needs to be munged, but + * NFS code. (Of course, the OTW NFS protocol still needs to be munged, but * that is a(whole)nother story.) This is a feature. */ |