Messages in this thread Patch in this message | | | Date | Tue, 16 Sep 2003 13:05:11 +1000 | From | Michael Still <> | Subject | [2.6 Patch] Kernel-doc updates 8 of 15 -- /fs/locks.c |
| |
This patch removes kernel-doc errors reported whilst doing a make mandocs on 2.6-test4-bk5
Linus, please apply.
Cheers, Mikal
--------------------------
diff -Nur linux-2.6.0-test4-bk5-mandocs/fs/locks.c linux-2.6.0-test4-bk5-mandocs_tweaks/fs/locks.c --- linux-2.6.0-test4-bk5-mandocs/fs/locks.c 2003-09-04 10:57:06.000000000 +1000 +++ linux-2.6.0-test4-bk5-mandocs_tweaks/fs/locks.c 2003-09-06 20:31:11.000000000 +1000 @@ -928,10 +928,10 @@ * locks_mandatory_area - Check for a conflicting lock * @read_write: %FLOCK_VERIFY_WRITE for exclusive access, %FLOCK_VERIFY_READ * for shared - * @inode: the file to check - * @file: how the file was opened (if it was) - * @offset: start of area to check - * @count: length of area to check + * @inode: the file to check + * @filp: how the file was opened (if it was) + * @offset: start of area to check + * @count: length of area to check * * Searches the inode's list of locks to find any POSIX locks which conflict. * This function is called from locks_verify_area() and @@ -1119,6 +1119,7 @@ /** * lease_get_mtime * @inode: the inode + * @time: pointer to a timespec which will contain the last modified time * * This is to force NFS clients to flush their caches for files with * exclusive leases. The justification is that if someone has an @@ -1720,6 +1721,7 @@ /** * posix_unblock_lock - stop waiting for a file lock + * @filp: how the file was opened * @waiter: the lock which was waiting * * lockd needs to block waiting for locks. --
Michael Still (mikal@stillhq.com) | "All my life I've had one dream, http://www.stillhq.com | to achieve my many goals" UTC + 10 | -- Homer Simpson
------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |