Skip to content

Commit ba4c74f

Browse files
bagasmebrauner
authored andcommitted
VFS: fix __start_dirop() kernel-doc warnings
Sphinx report kernel-doc warnings: WARNING: ./fs/namei.c:2853 function parameter 'state' not described in '__start_dirop' WARNING: ./fs/namei.c:2853 expecting prototype for start_dirop(). Prototype was for __start_dirop() instead Fix them up. Fixes: ff7c4ea ("VFS: add start_creating_killable() and start_removing_killable()") Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Link: https://patch.msgid.link/20251219024620.22880-3-bagasdotme@gmail.com Reviewed-by: Jeff Layton <jlayton@kernel.org> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Christian Brauner <brauner@kernel.org>
1 parent b0f5804 commit ba4c74f

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

fs/namei.c

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2834,10 +2834,11 @@ static int filename_parentat(int dfd, struct filename *name,
28342834
}
28352835

28362836
/**
2837-
* start_dirop - begin a create or remove dirop, performing locking and lookup
2837+
* __start_dirop - begin a create or remove dirop, performing locking and lookup
28382838
* @parent: the dentry of the parent in which the operation will occur
28392839
* @name: a qstr holding the name within that parent
28402840
* @lookup_flags: intent and other lookup flags.
2841+
* @state: task state bitmask
28412842
*
28422843
* The lookup is performed and necessary locks are taken so that, on success,
28432844
* the returned dentry can be operated on safely.

0 commit comments

Comments
 (0)