From fe166a35ff0c70708abd1bac2153063f2828fa35 Mon Sep 17 00:00:00 2001
From: Attilio Rao <attilio@FreeBSD.org>
Date: Thu, 10 Jan 2008 01:23:59 +0000
Subject: [PATCH] Update vn_lock() prototype accordingly with the 'thread'
 argument removal.

---
 share/man/man9/VOP_LOCK.9 | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/share/man/man9/VOP_LOCK.9 b/share/man/man9/VOP_LOCK.9
index 36fbe4e9a75..78fda97c372 100644
--- a/share/man/man9/VOP_LOCK.9
+++ b/share/man/man9/VOP_LOCK.9
@@ -28,7 +28,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd December 27, 2007
+.Dd January 10, 2008
 .Os
 .Dt VOP_LOCK 9
 .Sh NAME
@@ -48,7 +48,7 @@
 .Ft int
 .Fn VOP_ISLOCKED "struct vnode *vp" "struct thread *td"
 .Ft int
-.Fn vn_lock "struct vnode *vp" "int flags" "struct thread *td"
+.Fn vn_lock "struct vnode *vp" "int flags"
 .Sh DESCRIPTION
 These calls are used to serialize access to the file system, such as
 to prevent two writes to the same file from happening at the
@@ -110,6 +110,9 @@ Kernel code should use
 to lock a vnode rather than calling
 .Fn VOP_LOCK
 directly.
+.Fn vn_lock
+also doesn't want a thread specified as argument but it
+assumes curthread to be used.
 .Sh RETURN VALUES
 Zero is returned on success, otherwise an error is returned.
 .Sh PSEUDOCODE